CVE-2026-80611: Linux kernel · ACPI: processor_idle: Mark LPI enter functions as __cpuidle
Affects Linux kernelSource GCVE Database
Not known to be exploited · fixed in 6.8.0-147.147 : update Linux kernel when convenient.
Data as of 28 Oct 2026, 01:00 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- Patch
- Available – fixed in 6.8.0-147.147, 6.8.0-1067.70, 7.0.0-1014.14~24.04.1 +25
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-8888-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8889-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8887-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8888-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8887-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8887-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8917-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8918-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2026-80611 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-80611 (opens in a new tab)
- git.kernel.org/linus/956ca5d72c76504824c8eb601879da9476973e15 (opens in a new tab)
- git.kernel.org/stable/c/10f675902a5fc88ccfe34bb8aa37de50806b03b1 (opens in a new tab)
- git.kernel.org/stable/c/5b6165d7ec38477e8cfa41bfa464959957953822 (opens in a new tab)
- git.kernel.org/stable/c/8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9 (opens in a new tab)
- git.kernel.org/stable/c/956ca5d72c76504824c8eb601879da9476973e15 (opens in a new tab)
- ubuntu.com/security/notices/USN-8888-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8889-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8887-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8888-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8887-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8887-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8917-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8918-1 (opens in a new tab)