cve/published/2025/CVE-2025-37831.mbox

From bippy-1.2.0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@kernel.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2025-37831: cpufreq: apple-soc: Fix null-ptr-deref in apple_soc_cpufreq_get_rate()

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

cpufreq: apple-soc: Fix null-ptr-deref in apple_soc_cpufreq_get_rate()

cpufreq_cpu_get_raw() can return NULL when the target CPU is not present
in the policy->cpus mask. apple_soc_cpufreq_get_rate() does not check
for this case, which results in a NULL pointer dereference.

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


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

	Issue introduced in 6.2 with commit 6286bbb40576ffadfde206c332b61345c19af57f and fixed in 6.6.89 with commit 1053dcf8a504d4933bb3f73df22bc363298d194b
	Issue introduced in 6.2 with commit 6286bbb40576ffadfde206c332b61345c19af57f and fixed in 6.12.26 with commit fbdba5f37413dbc09d82ad7235e5b7a2fb8e0f75
	Issue introduced in 6.2 with commit 6286bbb40576ffadfde206c332b61345c19af57f and fixed in 6.14.5 with commit 01e86ea22610d98ae6141e428019a6916e79f725
	Issue introduced in 6.2 with commit 6286bbb40576ffadfde206c332b61345c19af57f and fixed in 6.15 with commit 9992649f6786921873a9b89dafa5e04d8c5fef2b

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-37831
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/cpufreq/apple-soc-cpufreq.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/1053dcf8a504d4933bb3f73df22bc363298d194b
	https://git.kernel.org/stable/c/fbdba5f37413dbc09d82ad7235e5b7a2fb8e0f75
	https://git.kernel.org/stable/c/01e86ea22610d98ae6141e428019a6916e79f725
	https://git.kernel.org/stable/c/9992649f6786921873a9b89dafa5e04d8c5fef2b