CVE-2025-38113

ACPI: CPPC: Fix NULL pointer dereference when nosmp is used

MEDIUM

5.5

CVSS Score

Published: July 3, 2025 at 08:35 AM UTC

Updated: June 17, 2026 at 09:16 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

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 ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

11.0

Linux Kernel · Linux

95%

5.19 ≤ v < 6.1.1425.19 ≤ v < 6.12.345.19 ≤ v < 6.15.35.19 ≤ v < 6.165.19 ≤ v < 6.6.946.13 ≤ v < 6.15.36.2 ≤ v < 6.6.946.7 ≤ v < 6.12.343cc30dd00a580ca0c9c0b01639841cfd72d101295.19 6.16 rc1

Vendor states this is fixed in 15eece6c5b05e5f9db0711978c3e3b7f1a2cfe12 (fixed)

Vendor states this is fixed in 1a677d0ceb4a5d62117b711a8b2e0aee80d33015 (fixed)

Vendor states this is fixed in 32a48db4cf28ea087214c261da8476db218d08bd (fixed)

Vendor states this is fixed in 356d09c7f5bf525086002a34f8bae40b134d1611 (fixed)

Vendor states this is fixed in c6dad167aade4bf0bef9130f2f149f4249fc4ad0 (fixed)

Vendor states this is fixed in 5.19 (unaffected)

Vendor states this is fixed in 6.1.142 (unaffected)

Vendor states this is fixed in 6.12.34 (unaffected)

Vendor states this is fixed in 6.15.3 (unaffected)

Vendor states this is fixed in 6.16 (unaffected)

Vendor states this is fixed in 6.6.94 (unaffected)