ACPI: processor_idle: Mark LPI enter functions as __cpuidle
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a36a7fecfe6071732075ad5aa31196adce13181b · < 956ca5d72c76504824c8eb601879da9476973e15| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ACPI Low Power Idle entry path can emit an RCU warning when function tracing or Kprobes is enabled. This occurs because tracing runs after RCU has been disabled for the local CPU; the input does not describe an attacker action or access requirements.
Engineers running Linux kernels with ACPI Low Power Idle and function tracing or Kprobes enabled should check their kernel; affected versions are not specified.