s390/vfio_ccw: Move cp cleanup out of not operational
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 204b394a23ad5e30944f23518e21e844614da2ff · < 0c11f61a876ed6fcca53d442ed3f33ea8362a0f9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/vfio_ccw: Move cp cleanup out of not operational
The fsm_notoper() routine is called when the device has been lost, and is (by definition) no longer operational. Since this can happen asynchronously from the normal behavior of the driver, the cleanup may happen when holding other locks in the calling sequence (notably, the cio subchannel lock).
Push the cleanup of the private->cp resources to a workqueue, where it can be done out from under that lock sequence and a future patch can safely manage the locking requirements.
From the CVE record · Linux
The Linux kernel's s390/vfio_ccw driver can clean up private resources while other locks are held when a device is lost asynchronously. The input does not specify an attacker action, access requirements, or a user-interaction requirement.
Engineers running Linux kernels that use s390/vfio_ccw should check their versions; affected versions were not provided.