Look up another CVE · open CVE-2026-80552 in the interactive tracker
CVE-2026-80552
s390/vfio_ccw: Ensure index for read/write regions are within range
Published 2026-08-26 (2 months ago) by the Linux kernel CNA. Subsystem drivers/s390. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2026-80552 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4777-1 · 2026-09-08 · text | 6.1.187-1 | Update the kernel and reboot. DLA-4777-1 shipped the fix on 2026-09-08, in 6.1.187-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.105-1 | Update the kernel and reboot. Fixed in 6.12.105-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4788-1 · 2026-09-19 · text | 6.12.107-1~deb12u1 | Update the kernel and reboot. DLA-4788-1 shipped the fix on 2026-09-19, in 6.12.107-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/s390/cio/vfio_ccw_async.c
drivers/s390/cio/vfio_ccw_chp.c
drivers/s390/cio/vfio_ccw_ops.c
- What this is
- S390 VFIO-CCW DRIVERMAINTAINERS section matched on drivers/s390/cio/vfio_ccw* · linux-s390@vger.kernel.org · Supported
Check it on the machine
grep -wE 'CONFIG_S390|CONFIG_VFIO_CCW' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian does not build this code. In 5 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sid, bookworm · linux-6.12n
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_S390, CONFIG_VFIO_CCW
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-26 (2 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.18%, higher than 6.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/s390
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.2 | 5.15.218 | 3acbedf5c0b8 |
| 5.2 | 6.1.184 | d3b1e38404b2 |
| 5.2 | 6.6.153 | 79ea5e0c4c8a |
| 5.2 | 6.12.105 | d597fa127380 |
| 5.2 | 6.18.46 | 649badf3a2fd |
| 5.2 | 7.1.10 | 988d9b5be3c2 |
| 5.2 | 7.2 | 9f5f9a78fedc |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4788-1 | 2026-09-19 | bookworm 6.12.107-1~deb12u1 | tracker |
| DLA-4777-1 | 2026-09-08 | bookworm 6.1.187-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The flaw is reached only via local VFIO mediated-device syscalls (read/write on a vfio-ccw device fd and VFIO_DEVICE_GET_REGION_INFO ioctl); vfio-ccw has no network, Bluetooth, or physical-bus entry point.
- AC:LAttack complexity, low
- An attacker with an open vfio-ccw fd can deterministically supply crafted file offsets encoding out-of-range region indexes to read/write/ioctl handlers, or race close/teardown against region access, without depending on uncontrollable kernel layout or rare timing.
- PR:LPrivileges required, low
- Exploitation requires an opened vfio-ccw mdev device fd (typical QEMU/libvirt VM operator or delegated /dev/vfio holder on IBM Z passthrough); mdev creation is admin setup, but triggering the OOB paths needs only that delegated VFIO client, not init-namespace root.
- UI:NUser interaction, none
- No separate victim action is required beyond the attacker (or their QEMU process) issuing crafted VFIO read/write/ioctl calls on an already-assigned passthrough device; no mount, click, or other user cooperation is needed at trigger time.
- S:CScope, changed
- On IBM Z/LinuxONE, vfio-ccw exists to pass DASD/CCW subchannels into KVM guests; OOB region indexing in host read/write/ioctl corrupts hypervisor kernel memory outside the guest VM security boundary, enabling cross-tenant host compromise.
- C:HConfidentiality impact, high
- Missing bounds checks and array_index_nospec on region[i] let out-of-range indexes make copy_to_user read from adjacent kernel heap/metadata beyond the region array, providing arbitrary kernel memory disclosure primitives.
- I:HIntegrity impact, high
- Out-of-range region indexes route copy_from_user writes to wrong kernel objects (cmd_region, schib_region, crw_region, or adjacent heap), enabling heap corruption and exploitable arbitrary kernel write or control-flow hijack.
- A:HAvailability impact, high
- Out-of-bounds access to freed or invalid region metadata during concurrent device close, or corrupting vfio_ccw_private adjacent structures, can immediately oops or panic the host kernel.