CVE-2026-80552 json
s390/vfio_ccw: Ensure index for read/write regions are within range
published 2026-08-26 2 mo ago modified 2026-10-16 23 d ago also EUVD-2026-66467
- cvss
- 8.8
- 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: Ensure index for read/write regions are within range
The introduction of the capability chain rightly clamped the region indexes to the range of the capabilities itself, but neglected to do so for the existing read/write regions which should also be enforced.
Patch / fix
- Linux Linux 5.15.218, 6.1.184, 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-80552
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-80552
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/3acbedf5c0b8e0971f0de423c05cc02bbf6ddb99 commit
- git.kernel.org/stable/c/d3b1e38404b22df5a1f93019f2bb656feaad5ae3 commit
- git.kernel.org/stable/c/79ea5e0c4c8a9842ae85f45062d947b3297dfc07 commit
- git.kernel.org/stable/c/d597fa1273802941c7801202135976fecc29672b commit
- git.kernel.org/stable/c/649badf3a2fd8929e40198603a2cb21b74c21700 commit
- git.kernel.org/stable/c/988d9b5be3c2c4baf9457ce8e11b477e13eb9fcf commit
- git.kernel.org/stable/c/9f5f9a78fedc45bc29d6a0a64e3a3472361afae5 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-80552 updated cvss 5.5
kernel: s390/vfio_ccw: Ensure index for read/write regions are within range
-
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.13% 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.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/3acbedf5c0b8e0971f0de423c05cc02bbf6ddb99
- git.kernel.org /stable/c/d3b1e38404b22df5a1f93019f2bb656feaad5ae3
- git.kernel.org /stable/c/79ea5e0c4c8a9842ae85f45062d947b3297dfc07
- git.kernel.org /stable/c/d597fa1273802941c7801202135976fecc29672b
- git.kernel.org /stable/c/649badf3a2fd8929e40198603a2cb21b74c21700
- git.kernel.org /stable/c/988d9b5be3c2c4baf9457ce8e11b477e13eb9fcf
- git.kernel.org /stable/c/9f5f9a78fedc45bc29d6a0a64e3a3472361afae5
Sources
- CVE List CVE-2026-80552
- NVD CVE-2026-80552
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.