CVE-2026-80548

HIGHCVSS 8.8/10

Last modified

CVE-2026-80548 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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..

Description

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.

Metrics

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 4f76617378ee97c557b526cb58d3c61eb0a9c963, < dab6a6627b0b0cce23653e99c7b0bf8c6cfd82e0; >= 4f76617378ee97c557b526cb58d3c61eb0a9c963, < 56d7488533ceac4e986e96e15c9e487a2245bc01; >= 4f76617378ee97c557b526cb58d3c61eb0a9c963, < f72a51810d49411bd8cad0c2df8592320a2fe5cc; >= 4f76617378ee97c557b526cb58d3c61eb0a9c963, < 2ba9efdf9ebedc4e54df4b56aa3b43a65f7967cd; >= 4f76617378ee97c557b526cb58d3c61eb0a9c963, < b6aecea4b2b246f9fbd98a5712daa1193a60818e; >= 4f76617378ee97c557b526cb58d3c61eb0a9c963, < 2a5ac0c0f1f7da33929211a2e41911bf72ee35d8; >= 4f76617378ee97c557b526cb58d3c61eb0a9c963, < 34f4feff3e90bd09308fad0974e97113b23b812a
LinuxLinux5.2

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80548?
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.
How severe is CVE-2026-80548?
CVE-2026-80548 has a CVSS score of 8.8/10 (HIGH severity).
How do I fix CVE-2026-80548?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-80548?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST