linux-cve-announce - CVE-2025-38113: ACPI: CPPC: Fix NULL pointer dereference when nosmp is used

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025070325-CVE-2025-38113-d080@gregkh>
Date: Thu,  3 Jul 2025 10:35:30 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38113: ACPI: CPPC: Fix NULL pointer dereference when nosmp is used

From: Greg Kroah-Hartman <gregkh@...nel.org>

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 ]

The Linux kernel CVE team has assigned CVE-2025-38113 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.19 with commit 3cc30dd00a580ca0c9c0b01639841cfd72d10129 and fixed in 6.1.142 with commit 356d09c7f5bf525086002a34f8bae40b134d1611
	Issue introduced in 5.19 with commit 3cc30dd00a580ca0c9c0b01639841cfd72d10129 and fixed in 6.6.94 with commit c6dad167aade4bf0bef9130f2f149f4249fc4ad0
	Issue introduced in 5.19 with commit 3cc30dd00a580ca0c9c0b01639841cfd72d10129 and fixed in 6.12.34 with commit 32a48db4cf28ea087214c261da8476db218d08bd
	Issue introduced in 5.19 with commit 3cc30dd00a580ca0c9c0b01639841cfd72d10129 and fixed in 6.15.3 with commit 1a677d0ceb4a5d62117b711a8b2e0aee80d33015
	Issue introduced in 5.19 with commit 3cc30dd00a580ca0c9c0b01639841cfd72d10129 and fixed in 6.16-rc2 with commit 15eece6c5b05e5f9db0711978c3e3b7f1a2cfe12

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-38113
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/acpi/cppc_acpi.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/356d09c7f5bf525086002a34f8bae40b134d1611
	https://git.kernel.org/stable/c/c6dad167aade4bf0bef9130f2f149f4249fc4ad0
	https://git.kernel.org/stable/c/32a48db4cf28ea087214c261da8476db218d08bd
	https://git.kernel.org/stable/c/1a677d0ceb4a5d62117b711a8b2e0aee80d33015
	https://git.kernel.org/stable/c/15eece6c5b05e5f9db0711978c3e3b7f1a2cfe12