ACPI: CPPC: Fix NULL pointer dereference when nosmp is used
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ACPI: CPPC: Fix NULL pointer dereference when nosmp is used
With nosmp in cmdline, other CPUs are not brought up, leaving their cpc_desc_ptr NULL. CPU0's iteration via for_each_possible_cpu() dereferences these NULL pointers, causing panic.
Panic backtrace:
[ 0.401123] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000b8 ... [ 0.403255] [<ffffffff809a5818>] cppc_allow_fast_switch+0x6a/0xd4 ... Kernel panic - not syncing: Attempted to kill init!
[ rjw: New subject ]
From the CVE record · Linux
The Linux kernel’s ACPI CPPC code can dereference a NULL pointer when the system boots with `nosmp`, causing a kernel panic. The input does not describe an attacker path, authentication requirement, or user-interaction requirement.
Operators running Linux kernels with ACPI CPPC should check their kernel, particularly if they use the `nosmp` boot option; affected versions are not specified.