VulnerabilityPublished 28 Aug 2026Updated 21 Oct 2026

CVE-2026-80611: Linux kernel · ACPI: processor_idle: Mark LPI enter functions as __cpuidle

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2, 956ca5d72c76504824c8eb601879da9476973e15, 10f675902a5fc88ccfe34bb8aa37de50806b03b1 +2

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ a36a7fecfe6071732075ad5aa31196adce13181b, < c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2	Fixed in c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2
LinuxLinux	Affected ≥ a36a7fecfe6071732075ad5aa31196adce13181b, < 956ca5d72c76504824c8eb601879da9476973e15	Fixed in 956ca5d72c76504824c8eb601879da9476973e15
LinuxLinux	Affected ≥ a36a7fecfe6071732075ad5aa31196adce13181b, < 10f675902a5fc88ccfe34bb8aa37de50806b03b1	Fixed in 10f675902a5fc88ccfe34bb8aa37de50806b03b1
LinuxLinux	Affected ≥ a36a7fecfe6071732075ad5aa31196adce13181b, < 8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9	Fixed in 8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9
LinuxLinux	Affected ≥ a36a7fecfe6071732075ad5aa31196adce13181b, < 5b6165d7ec38477e8cfa41bfa464959957953822	Fixed in 5b6165d7ec38477e8cfa41bfa464959957953822
LinuxLinux	Affected =4.8	Fixed in–

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

Community reviews

Loading reviews…