CVE-2026-80548s390/vfio_ccw: Selectively expand io_mutex
- 8.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 51 days later
· 51 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected 4f76617378ee97c557b526cb58d3c61eb0a9c963 – < dab6a6627b0b0cce23653e99c7b0bf8c6cfd82e0
- affected 4f76617378ee97c557b526cb58d3c61eb0a9c963 – < 56d7488533ceac4e986e96e15c9e487a2245bc01
- affected 4f76617378ee97c557b526cb58d3c61eb0a9c963 – < f72a51810d49411bd8cad0c2df8592320a2fe5cc
- affected 4f76617378ee97c557b526cb58d3c61eb0a9c963 – < 2ba9efdf9ebedc4e54df4b56aa3b43a65f7967cd
- affected 4f76617378ee97c557b526cb58d3c61eb0a9c963 – < b6aecea4b2b246f9fbd98a5712daa1193a60818e
- affected 4f76617378ee97c557b526cb58d3c61eb0a9c963 – < 2a5ac0c0f1f7da33929211a2e41911bf72ee35d8
- affected 4f76617378ee97c557b526cb58d3c61eb0a9c963 – < 34f4feff3e90bd09308fad0974e97113b23b812a
- affected 5.2
- unaffected < 5.2
- unaffected 5.15.218 – ≤ 5.15.*
- unaffected 6.1.185 – ≤ 6.1.*
- unaffected 6.6.153 – ≤ 6.6.*
- unaffected 6.12.105 – ≤ 6.12.*
- unaffected 6.18.46 – ≤ 6.18.*
- unaffected 7.1.10 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/dab6a6627b0b0cce23653e99c7b0bf8c6cfd82e0 (opens in a new tab)
- https://git.kernel.org/stable/c/56d7488533ceac4e986e96e15c9e487a2245bc01 (opens in a new tab)
- https://git.kernel.org/stable/c/f72a51810d49411bd8cad0c2df8592320a2fe5cc (opens in a new tab)
- https://git.kernel.org/stable/c/2ba9efdf9ebedc4e54df4b56aa3b43a65f7967cd (opens in a new tab)
- https://git.kernel.org/stable/c/b6aecea4b2b246f9fbd98a5712daa1193a60818e (opens in a new tab)
- https://git.kernel.org/stable/c/2a5ac0c0f1f7da33929211a2e41911bf72ee35d8 (opens in a new tab)
- https://git.kernel.org/stable/c/34f4feff3e90bd09308fad0974e97113b23b812a (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-66463 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80548)Record last updated .