cve.bz

CVE-2026-80548 linux linux

8.8 highEPSS 0.1%Fix available

High (8.8) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: s390/vfio_ccw: Selectively expand io_mutex The io_mutex was defined to serialize the io_regions, but then has also sort of been associated with the I/O themselves because of the close relationship they share. With the handful of races that are possible, the choices are either to: A) expand the scope of io_mutex to close these remaining windows, or B) reduce the scope of io_mutex to just io_region, and introduce a new lock mechanism for the remaining I/O resources This patch implements A, since B brings with it a lot more interactions that would need to be tracked and kept in a correct hierarchy. It also takes advantage of the workqueue element for cp_free() that now gets called out of fsm_notoper(), which could be invoked out of an interrupt context and thus cannot acquire a mutex itself.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.15.218
  • Linux Linux: fixed in 6.1.185
  • Linux Linux: fixed in 6.6.153
  • Linux Linux: fixed in 6.12.105
  • Linux Linux: fixed in 6.18.46
  • Linux Linux: fixed in 7.1.10
  • Linux Linux: fixed in 7.2
  • Debian, Ubuntu, SUSE, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-80548 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80548?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80548?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80548 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.2 and later

Fixed in

ProductRelease lineFixed in
Linux5.155.15.218
Linux6.16.1.185
Linux6.66.6.153
Linux6.126.12.105
Linux6.186.18.46
Linux7.17.1.10
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.187-1DEBIAN-CVE-2026-80548
Debian12linux-6.126.12.107-1~deb12u1DEBIAN-CVE-2026-80548
Debian13linux6.12.105-1DEBIAN-CVE-2026-80548
Debian14linux7.1.10-1DEBIAN-CVE-2026-80548
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-80548
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-80548
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-80548
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-80548 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-80548 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-80548 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-80548 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-80548 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-80548 USN-8962-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-80548 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-80548 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-80548 USN-9024-1
80 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise Server for NVIDIA 16.1kernel-nvidia64kb, kernel-source-nvidia6.12.0-160100.7.1SUSE-SU-2026:24705-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia6.12.0-160100.7.1openSUSE-SU-2026:22307-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-80548
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-80548
Alpaquitastreamlinux-lts6.18.46-r0BELL-CVE-2026-80548

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate impact flaw was found in the Linux kernel's s390/vfio_ccw driver, affecting Red Hat Enterprise Linux 9 and 10 and Red Hat In-Vehicle OS 2. The io_mutex was not consistently held across the channel-program and I/O lifecycle paths, so operations such as I/O completion, device close, not-operational cleanup, or CRW handling could race against channel-program teardown. A local attacker with access to a vfio_ccw (VFIO-CCW mediated) device on an IBM s390x system could exploit this race to cause use-after-free or list corruption in kernel I/O structures, resulting at minimum in a kernel crash and denial of service. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those streams. For the affected Red Hat Enterprise Linux 9 and 10 and Red Hat In-Vehicle OS 2 streams the fix has been deferred: reliably triggering this timing-dependent race requires local access to a vfio_ccw passthrough device and the practical impact is denial of service, so the fix will be delivered in a future scheduled kernel update rather than an immediate erratum. The residual risk is a local kernel panic on s390x systems that use vfio_ccw device passthrough. Red Hat has rated this flaw Moderate severity (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), which differs from the upstream CVE.org rating of Important (8.8) because exploitation requires local access and privileges on a system configured with vfio_ccw devices and Red Hat's assessment limits the impact to availability.

Red Hat's mitigation

This flaw can only be triggered through the vfio_ccw driver on IBM s390x systems. As a mitigation, avoid using vfio-ccw passthrough: do not create or assign vfio_ccw mediated devices to guests or untrusted local processes, and restrict local access to vfio_ccw devices, until a kernel containing the fix is applied. Systems that do not use vfio-ccw mediated devices are not exposed to this flaw.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80548.

References

Check your stackJSON