CVE-2026-80611 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
- EPSS
- 0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 6.1.191
- Linux Linux: fixed in 6.6.160
- Linux Linux: fixed in 6.12.97
- Linux Linux: fixed in 6.18.40
- Linux Linux: fixed in 7.1.5
- Linux Linux: fixed in 7.2
- Debian, Ubuntu, SUSE, openSUSE, Azure Linux, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-80611 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80611?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80611?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-80611 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.
| Product | Affected |
|---|---|
| Linux | 4.8 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.1 | 6.1.191 |
| Linux | 6.6 | 6.6.160 |
| Linux | 6.12 | 6.12.97 |
| Linux | 6.18 | 6.18.40 |
| Linux | 7.1 | 7.1.5 |
| Linux | later releases | 7.2 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.192-1 | DEBIAN-CVE-2026-80611 |
| Debian | 13 | linux | 6.12.100-1 | DEBIAN-CVE-2026-80611 |
| Debian | 14 | linux | 7.1.5-1 | DEBIAN-CVE-2026-80611 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-80611 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-80611 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-80611 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 48 more | no fix listed | UBUNTU-CVE-2026-80611 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-80611 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-80611 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-80611 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-80611 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-hwe-6.8 | 6.8.0-149.149~22.04.1 | UBUNTU-CVE-2026-80611 USN-9066-1 |
| Ubuntu | 22.04:LTS | linux-ibm-6.8 | 6.8.0-1069.70~22.04.1 | UBUNTU-CVE-2026-80611 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-149.149.1~22.04.1 | UBUNTU-CVE-2026-80611 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-oracle-6.8 | 6.8.0-1067.71~22.04.1 | UBUNTU-CVE-2026-80611 USN-9025-1 |
| 47 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| SUSE | Linux Enterprise High Availability Extension 16.0 | kernel-default | 6.12.0-160000.41.1 | SUSE-SU-2026:24651-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-64kb, kernel-docs, kernel-syms and 6 more | 6.12.0-160000.41.1 | SUSE-SU-2026:24662-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-default-base | 6.12.0-160000.41.1.160000.2.32 | SUSE-SU-2026:24662-1 |
| SUSE | Linux Enterprise Server for NVIDIA 16.1 | kernel-nvidia64kb, kernel-source-nvidia | 6.12.0-160100.7.1 | SUSE-SU-2026:24705-1 |
| SUSE | Linux Micro 6.2 | kernel-default-base | 6.12.0-160000.41.1.160000.2.32 | SUSE-SU-2026:24643-1 |
| SUSE | Linux Micro 6.2 | kernel-rt, kernel-64kb, kernel-source and 1 more | 6.12.0-160000.41.1 | SUSE-SU-2026:24643-1 |
| SUSE | Linux Micro Extras 6.2 | kernel-syms, kernel-obs-build | 6.12.0-160000.41.1 | SUSE-SU-2026:24648-1 |
| openSUSE | Leap 16.0 | kernel-default-base | 6.12.0-160000.41.1.160000.2.31 | openSUSE-SU-2026:22266-1 |
| openSUSE | Leap 16.0 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160000.41.1 | openSUSE-SU-2026:22266-1 |
| openSUSE | Leap 16.1 | kernel-default-base | 6.12.0-160100.9.1.160100.3.14 | openSUSE-SU-2026:22309-1 |
| openSUSE | Leap 16.1 | kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia | 6.12.0-160100.7.1 | openSUSE-SU-2026:22307-1 |
| openSUSE | Leap 16.1 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160100.9.1 | openSUSE-SU-2026:22309-1 |
| Azure Linux | 3 | kernel | 6.6.161.1-1 | AZL-98063 |
| Alpaquita | 23 | linux-lts | 6.1.191-r0 | BELL-CVE-2026-80611 |
| Alpaquita | 25 | linux-lts | 6.12.103-r0 | BELL-CVE-2026-80611 |
| Alpaquita | stream | linux-lts | 6.18.43-r0 | BELL-CVE-2026-80611 |
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; Microsoft's Azure Linux vulnerability data, MIT; 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 Low.
A flaw of low impact was found in the Linux kernel's ACPI processor idle handling as shipped in Red Hat Enterprise Linux and Red Hat In-Vehicle OS. When kernel tracing features such as function tracing (ftrace) or Kprobes are enabled, entering an ACPI Low Power Idle (LPI) state can trigger a Read-Copy-Update (RCU) warning: the acpi_idle_lpi_enter() function runs in the cpuidle path after RCU has already been disabled for the local CPU, while ftrace's function_trace_call() expects RCU to be actively watching before recording trace data. The primary consequence is an RCU splat, warning output, and possible system instability or unexpected behavior limited to the tracing path; there is no evidence of memory corruption, information disclosure, or privilege escalation, and triggering requires local access with the privileges needed to enable kernel tracing. For this reason Red Hat rates the impact of this flaw as low despite the CVSS 3.1 base score of 5.5. The kernel and kernel-rt packages in Red Hat Enterprise Linux 8, 9, and 10, and the Red Hat In-Vehicle OS 2 kernels, are affected; given the low impact and diagnostic nature of the issue, the fix is currently deferred for these streams, leaving a residual risk of trace-induced RCU warnings and log noise during idle entry on systems running with tracing enabled. Red Hat Enterprise Linux 7 kernels are not affected because the vulnerable code is not present, and Red Hat Enterprise Linux 6 ELS is out of support scope.
This issue only manifests when kernel function tracing (ftrace) or Kprobes are enabled, which is not the default configuration. Disabling or avoiding function tracing and Kprobe instrumentation on affected systems prevents the RCU warnings from being triggered during ACPI Low Power Idle entry.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Out of support scope | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 8 | kernel-rt | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Fix 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-80611.
References
- https://git.kernel.org/stable/c/10f675902a5fc88ccfe34bb8aa37de50806b03b1
- https://git.kernel.org/stable/c/5b6165d7ec38477e8cfa41bfa464959957953822
- https://git.kernel.org/stable/c/8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9
- https://git.kernel.org/stable/c/8ca5dfe4249bbb6bd34f37d16c2ea933c31f6a2a
- https://git.kernel.org/stable/c/956ca5d72c76504824c8eb601879da9476973e15
- https://git.kernel.org/stable/c/c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2