CVE-2026-80611

CVE CVE-2026-80611EUVD EUVD-2026-67487Published 2026-08-28T06:48:33.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 0; patch: 7.1.5; a36a7fecfe6071732075ad5aa31196adce13181b <8bbe4dd7964552f74c271c3a8d95a4331a8ab5f9; patch: 6.12.97; patch: 6.18.40; a36a7fecfe6071732075ad5aa31196adce13181b <956ca5d72c76504824c8eb601879da9476973e15; a36a7fecfe6071732075ad5aa31196adce13181b <10f675902a5fc88ccfe34bb8aa37de50806b03b1; patch: 7.2; a36a7fecfe6071732075ad5aa31196adce13181b <5b6165d7ec38477e8cfa41bfa464959957953822; 4.8

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.