CVE-2026-80549 json
s390/vfio_ccw: Move cp cleanup out of not operational
published 2026-08-26 2 mo ago modified 2026-10-16 23 d ago also EUVD-2026-66464
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
s390/vfio_ccw: Move cp cleanup out of not operational
The fsm_notoper() routine is called when the device has been lost, and is (by definition) no longer operational. Since this can happen asynchronously from the normal behavior of the driver, the cleanup may happen when holding other locks in the calling sequence (notably, the cio subchannel lock).
Push the cleanup of the private->cp resources to a workqueue, where it can be done out from under that lock sequence and a future patch can safely manage the locking requirements.
Patch / fix
- Linux Linux 6.1.185, 6.6.153, 6.12.105, 6.18.46, 7.1.10, 7.2
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.105-1
- linux Debian 14 7.1.10-1
- linux-6.12 Debian 12 6.12.107-1~deb12u1
debian advisories DEBIAN-CVE-2026-80549
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-80549
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/c9b85aa2cf73ea645e55e2c2670e0ddebfe1589b commit
- git.kernel.org/stable/c/f98a9890ca42f4223d2d4c50e0660af3e012fcb4 commit
- git.kernel.org/stable/c/4e3301e2a651d742c05914f6074a25b8e41bce19 commit
- git.kernel.org/stable/c/af1759d8e6e6da9ba94f30a2f92546f406899aa7 commit
- git.kernel.org/stable/c/56100baa0eb7055b1026dfa73e696e8066ff71fd commit
- git.kernel.org/stable/c/0c11f61a876ed6fcca53d442ed3f33ea8362a0f9 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-80549 updated cvss 5.5
kernel: s390/vfio_ccw: Move cp cleanup out of not operational
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 d ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/c9b85aa2cf73ea645e55e2c2670e0ddebfe1589b
- git.kernel.org /stable/c/f98a9890ca42f4223d2d4c50e0660af3e012fcb4
- git.kernel.org /stable/c/4e3301e2a651d742c05914f6074a25b8e41bce19
- git.kernel.org /stable/c/af1759d8e6e6da9ba94f30a2f92546f406899aa7
- git.kernel.org /stable/c/56100baa0eb7055b1026dfa73e696e8066ff71fd
- git.kernel.org /stable/c/0c11f61a876ed6fcca53d442ed3f33ea8362a0f9
Sources
- CVE List CVE-2026-80549
- NVD CVE-2026-80549
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.