s390/vfio_ccw: Selectively expand io_mutex
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.218, 6.1.185, 6.6.153, 6.12.105, 6.18.46, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 4f76617378ee97c557b526cb58d3c61eb0a9c963 · fixed in dab6a6627b0b0cce23653e99c7b0bf8c6cfd82e0; From 4f76617378ee97c557b526cb58d3c61eb0a9c963 · fixed in 56d7488533ceac4e986e96e15c9e487a2245bc01; From 4f76617378ee97c557b526cb58d3c61eb0a9c963 · fixed in f72a51810d49411bd8cad0c2df8592320a2fe5cc; From 4f76617378ee97c557b526cb58d3c61eb0a9c963 · fixed in 2ba9efdf9ebedc4e54df4b56aa3b43a65f7967cd; From 4f76617378ee97c557b526cb58d3c61eb0a9c963 · fixed in b6aecea4b2b246f9fbd98a5712daa1193a60818e; From 4f76617378ee97c557b526cb58d3c61eb0a9c963 · fixed in 2a5ac0c0f1f7da33929211a2e41911bf72ee35d8; From 4f76617378ee97c557b526cb58d3c61eb0a9c963 · fixed in 34f4feff3e90bd09308fad0974e97113b23b812a
- Linux Linux
5.2
- KernelLinux
From 5.2.0 · fixed in 5.15.218; From 5.16.0 · fixed in 6.1.185; From 6.2.0 · fixed in 6.6.153; From 6.7.0 · fixed in 6.12.105; From 6.13.0 · fixed in 6.18.46; From 6.19.0 · fixed in 7.1.10
References 7
git.kernel.org
- stable/c/dab6a6627b0b0cce23653e99c7b0bf8c6cfd82e0
- stable/c/56d7488533ceac4e986e96e15c9e487a2245bc01
- stable/c/f72a51810d49411bd8cad0c2df8592320a2fe5cc
- stable/c/2ba9efdf9ebedc4e54df4b56aa3b43a65f7967cd
- stable/c/b6aecea4b2b246f9fbd98a5712daa1193a60818e
- stable/c/2a5ac0c0f1f7da33929211a2e41911bf72ee35d8
- stable/c/34f4feff3e90bd09308fad0974e97113b23b812a