s390/vfio_ccw: Selectively expand io_mutex
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4f76617378ee97c557b526cb58d3c61eb0a9c963 · < 2a5ac0c0f1f7da33929211a2e41911bf72ee35d8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/vfio_ccw: Selectively expand io_mutex
The io_mutex was defined to serialize the io_regions, but then has also sort of been associated with the I/O themselves because of the close relationship they share.
With the handful of races that are possible, the choices are either to: A) expand the scope of io_mutex to close these remaining windows, or B) reduce the scope of io_mutex to just io_region, and introduce a new lock mechanism for the remaining I/O resources
This patch implements A, since B brings with it a lot more interactions that would need to be tracked and kept in a correct hierarchy. It also takes advantage of the workqueue element for cp_free() that now gets called out of fsm_notoper(), which could be invoked out of an interrupt context and thus cannot acquire a mutex itself.
From the CVE record · Linux
The Linux kernel's s390/vfio_ccw component has race windows involving io_mutex and I/O resources. The input does not specify what an attacker could do or whether exploitation requires network access, local access, authentication, or user interaction.
Engineers running the Linux kernel with s390/vfio_ccw should check their systems; affected versions are not specified.