ACPI: processor_idle: Mark LPI enter functions as __cpuidle
Summary
| CVE | CVE-2026-80611 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-28 08:16:45 UTC |
| Updated | 2026-08-28 08:16:45 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected a36a7fecfe6071732075ad5aa31196adce13181b 10f675902a5fc88ccfe34bb8aa37de50806b03b1 git |
Not specified |
| CNA |
Linux |
Linux |
affected a36a7fecfe6071732075ad5aa31196adce13181b 5b6165d7ec38477e8cfa41bfa464959957953822 git |
Not specified |
| CNA |
Linux |
Linux |
affected a36a7fecfe6071732075ad5aa31196adce13181b 8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9 git |
Not specified |
| CNA |
Linux |
Linux |
affected a36a7fecfe6071732075ad5aa31196adce13181b 956ca5d72c76504824c8eb601879da9476973e15 git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.8 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.8 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.97 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.40 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.5 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/10f675902a5fc88ccfe34bb8aa37de50806b03b1 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/956ca5d72c76504824c8eb601879da9476973e15 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/5b6165d7ec38477e8cfa41bfa464959957953822 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.