[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050915-CVE-2025-37841-1954@gregkh>
Date: Fri, 9 May 2025 08:42:19 +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-37841: pm: cpupower: bench: Prevent NULL dereference on malloc failure
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
pm: cpupower: bench: Prevent NULL dereference on malloc failure
If malloc returns NULL due to low memory, 'config' pointer can be NULL.
Add a check to prevent NULL dereference.
The Linux kernel CVE team has assigned CVE-2025-37841 to this issue.
Affected and fixed versions
===========================
Fixed in 5.4.293 with commit 34a9394794b0f97af6afedc0c9ee2012c24b28ed
Fixed in 5.10.237 with commit 79bded9d70142d2a11d931fc029afece471641db
Fixed in 5.15.181 with commit 0e297a02e03dceb2874789ca40bd4e65c5371704
Fixed in 6.1.135 with commit 87b9f0867c0afa7e892f4b30c36cff6bf2707f85
Fixed in 6.6.88 with commit 942a4b97fc77516678b1d8af1521ff9a94c13b3e
Fixed in 6.12.24 with commit f8d28fa305b78c5d1073b63f26db265ba8291ae1
Fixed in 6.13.12 with commit ceec06f464d5cfc0ba966225f7d50506ceb62242
Fixed in 6.14.3 with commit 5e38122aa3fd0f9788186e86a677925bfec0b2d1
Fixed in 6.15-rc1 with commit 208baa3ec9043a664d9acfb8174b332e6b17fb69
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-37841
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:
tools/power/cpupower/bench/parse.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/34a9394794b0f97af6afedc0c9ee2012c24b28ed
https://git.kernel.org/stable/c/79bded9d70142d2a11d931fc029afece471641db
https://git.kernel.org/stable/c/0e297a02e03dceb2874789ca40bd4e65c5371704
https://git.kernel.org/stable/c/87b9f0867c0afa7e892f4b30c36cff6bf2707f85
https://git.kernel.org/stable/c/942a4b97fc77516678b1d8af1521ff9a94c13b3e
https://git.kernel.org/stable/c/f8d28fa305b78c5d1073b63f26db265ba8291ae1
https://git.kernel.org/stable/c/ceec06f464d5cfc0ba966225f7d50506ceb62242
https://git.kernel.org/stable/c/5e38122aa3fd0f9788186e86a677925bfec0b2d1
https://git.kernel.org/stable/c/208baa3ec9043a664d9acfb8174b332e6b17fb69
Powered by blists - more mailing lists