Host compromise via asynchronous vfio-ccw cleanup race
Published Aug 26, 2026 · Updated Aug 27, 2026
A cleanup race in Linux kernel 6.0 through affected 7.1 releases allows local users with privileged VFIO access to compromise the host. The s390 vfio-ccw fsm_notoper() path calls cp_free() synchronously during an asynchronous not-operational transition while the CIO subchannel lock may be held, enabling deadlock or concurrent teardown of live channel-program metadata. Reachability requires an s390 host, an administrator-configured vfio-ccw mediated device, and CAP_SYS_ADMIN-level VFIO/IOMMU access; consequences include kernel hang, panic, memory disclosure, and kernel-state corruption.
Summary
What happened
A cleanup race in Linux kernel 6.0 through affected 7.1 releases allows local users with privileged VFIO access to compromise the host. The s390 vfio-ccw fsm_notoper() path calls cp_free() synchronously during an asynchronous not-operational transition while the CIO subchannel lock may be held, enabling deadlock or concurrent teardown of live channel-program metadata. Reachability requires an s390 host, an administrator-configured vfio-ccw mediated device, and CAP_SYS_ADMIN-level VFIO/IOMMU access; consequences include kernel hang, panic, memory disclosure, and kernel-state corruption.
The record
- CVE
- CVE-2026-80549
- Published
- Aug 26, 2026
- Updated
- Aug 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-833, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 26, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=204b394a23ad5e30944f23518e21e844614da2ff <0c11f61a876ed6fcca53d442ed3f33ea8362a0f9
- Affected versionversion=204b394a23ad5e30944f23518e21e844614da2ff <4e3301e2a651d742c05914f6074a25b8e41bce19
- Affected versionversion=204b394a23ad5e30944f23518e21e844614da2ff <56100baa0eb7055b1026dfa73e696e8066ff71fd
- Affected versionversion=204b394a23ad5e30944f23518e21e844614da2ff <af1759d8e6e6da9ba94f30a2f92546f406899aa7
- Affected versionversion=204b394a23ad5e30944f23518e21e844614da2ff <c9b85aa2cf73ea645e55e2c2670e0ddebfe1589b
- Affected versionversion=204b394a23ad5e30944f23518e21e844614da2ff <f98a9890ca42f4223d2d4c50e0660af3e012fcb4
- Affected versionversion=6.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo