CVE-2026-80554 in the critical feed json
s390/vfio_ccw: Limit the number of channel program segments
published 2026-08-26 2 mo ago modified 2026-10-30 9 d ago also EUVD-2026-66469
- cvss
- 9.3
- 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 3%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
s390/vfio_ccw: Limit the number of channel program segments
The processing of channel programs, and the CCWs within them, is done recursively. As such, there is an arbitrary (but not architectural) limit to the number of CCWs that can exist in a single channel program.
The vfio-ccw logic breaks these channel programs into segments whenever it encounters a Transfer-In-Channel (TIC) CCW, and the combined number of segments count towards the global limit. Impose an equivalent limit to the number of segments until such logic can be made non-recursive.
Patch / fix
- Linux Linux 6.1.191, 6.6.153, 6.12.105, 6.18.46, 7.1.10, 7.2
- 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-80554
- 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-80554
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/2ce00bb19db13606cda79f4b7aae4d9775de3096 commit
- git.kernel.org/stable/c/15fb4559a7fdf0b8725e433a71cfd03a1313a48b commit
- git.kernel.org/stable/c/a1625f66eaa1200068a0e2c05bc90e65182fc4e3 commit
- git.kernel.org/stable/c/06f4d6e5a8af6c2072e8cd39dbc512c683ca7fb2 commit
- git.kernel.org/stable/c/4ee94790490ae8dcc97df8597f07836c8a81bbcf commit
- git.kernel.org/stable/c/5405c90d6a47b3014e74ee0618a162449abbbc93 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-80554 updated cvss 5.5
kernel: s390/vfio_ccw: Limit the number of channel program segments
-
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 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/2ce00bb19db13606cda79f4b7aae4d9775de3096
- git.kernel.org /stable/c/15fb4559a7fdf0b8725e433a71cfd03a1313a48b
- git.kernel.org /stable/c/a1625f66eaa1200068a0e2c05bc90e65182fc4e3
- git.kernel.org /stable/c/06f4d6e5a8af6c2072e8cd39dbc512c683ca7fb2
- git.kernel.org /stable/c/4ee94790490ae8dcc97df8597f07836c8a81bbcf
- git.kernel.org /stable/c/5405c90d6a47b3014e74ee0618a162449abbbc93
Sources
- CVE List CVE-2026-80554
- NVD CVE-2026-80554
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.