CVE-2026-80611 json
ACPI: processor_idle: Mark LPI enter functions as __cpuidle
published 2026-08-28 2 mo ago modified 2026-10-30 10 d ago also EUVD-2026-67487
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ACPI: processor_idle: Mark LPI enter functions as __cpuidle
When function tracing or Kprobes is enabled, entering an ACPI Low Power Idle (LPI) state triggers the following RCU splat:
RCU not on for: acpi_idle_lpi_enter+0x4/0xd8 WARNING: CPU: 8 PID: 0 at include/linux/trace_recursion.h:162 function_trace_call+0x1e8/0x228
The acpi_idle_lpi_enter() function is invoked within the cpuidle path after RCU has already been disabled for the current local CPU. Consequently, ftrace's function_trace_call() expects RCU to be actively watching before recording trace data, emitting a warning if it is not.
Fix this by annotating acpi_idle_lpi_enter(), the generic __weak stub, and the RISC-V implementation of acpi_processor_ffh_lpi_enter() with __cpuidle. This moves these functions into the '.cpuidle.text' section, implicitly disabling ftrace instrumentation (notrace) along this sensitive path and preventing trace-induced RCU warnings during idle entry.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.97, 6.18.40, 7.1.5, 7.2
- linux Debian 13 6.12.100-1
- linux Debian 14 7.1.5-1
debian advisories DEBIAN-CVE-2026-80611
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gke Ubuntu 24.04 LTS 6.8.0-1066.74
- linux-gke Ubuntu 26.04 LTS 7.0.0-1008.9
ubuntu advisories UBUNTU-CVE-2026-80611
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/8ca5dfe4249bbb6bd34f37d16c2ea933c31f6a2a commit
- git.kernel.org/stable/c/c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2 commit
- git.kernel.org/stable/c/10f675902a5fc88ccfe34bb8aa37de50806b03b1 commit
- git.kernel.org/stable/c/5b6165d7ec38477e8cfa41bfa464959957953822 commit
- git.kernel.org/stable/c/8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9 commit
- git.kernel.org/stable/c/956ca5d72c76504824c8eb601879da9476973e15 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-80611 updated cvss 5.5
kernel: ACPI: processor_idle: Mark LPI enter functions as __cpuidle
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more 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 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 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
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/8ca5dfe4249bbb6bd34f37d16c2ea933c31f6a2a
- git.kernel.org /stable/c/c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2
- git.kernel.org /stable/c/10f675902a5fc88ccfe34bb8aa37de50806b03b1
- git.kernel.org /stable/c/5b6165d7ec38477e8cfa41bfa464959957953822
- git.kernel.org /stable/c/8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9
- git.kernel.org /stable/c/956ca5d72c76504824c8eb601879da9476973e15
Sources
- CVE List CVE-2026-80611
- NVD CVE-2026-80611
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.