Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected a36a7fecfe6071732075ad5aa31196adce13181b – < 8ca5dfe4249bbb6bd34f37d16c2ea933c31f6a2a
    • affected a36a7fecfe6071732075ad5aa31196adce13181b – < c17fe25dcb55ab94f6aa2930b7504ea666d5fcc2
    • affected a36a7fecfe6071732075ad5aa31196adce13181b – < 10f675902a5fc88ccfe34bb8aa37de50806b03b1
    • affected a36a7fecfe6071732075ad5aa31196adce13181b – < 5b6165d7ec38477e8cfa41bfa464959957953822
    • affected a36a7fecfe6071732075ad5aa31196adce13181b – < 8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9
    • affected a36a7fecfe6071732075ad5aa31196adce13181b – < 956ca5d72c76504824c8eb601879da9476973e15
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80611 badge
[![CVE-2026-80611](https://cveledger.app/badge/CVE-2026-80611.svg)](https://cveledger.app/cve/CVE-2026-80611)

Record last updated .