s390/vfio_ccw: Implement a crw lock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3f02cb2fd9d2d9e8762102886e3e4b51285797ee · < c76c4ee72bfc3824f4f491f18ed0323bf2e2daf9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/vfio_ccw: Implement a crw lock
Unlike the channel_program struct, which covers synchronous I/O submissions and asynchronous interrupts, the CRW region relies exclusively on asynchronous events coming from hardware.
Implement a lock to manage the list of those payloads, to ensure they are read cohesively.
From the CVE record · Linux
The Linux kernel’s s390/vfio_ccw CRW region lacked a lock for hardware-generated asynchronous payloads, so the payload list might not be read cohesively. The input does not specify what an attacker could do or whether exploitation requires network or local access, authentication, or user interaction.
Engineers running the Linux kernel with s390/vfio_ccw should check their deployments; affected versions were not provided.