[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061827-CVE-2025-38038-797b@gregkh>
Date: Wed, 18 Jun 2025 11:33:34 +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-38038: cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost
set_boost is a per-policy function call, hence a driver wide lock is
unnecessary. Also this mutex_acquire can collide with the mutex_acquire
from the mode-switch path in status_store(), which can lead to a
deadlock. So, remove it.
The Linux kernel CVE team has assigned CVE-2025-38038 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.31 with commit 61e931ee145eeab8196e585ff4334870b130b744
Fixed in 6.14.9 with commit cd347d071713234586762d79c5a691785e9be418
Fixed in 6.15 with commit db1cafc77aaaf871509da06f4a864e9af6d6791f
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-38038
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/amd-pstate.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/61e931ee145eeab8196e585ff4334870b130b744
https://git.kernel.org/stable/c/cd347d071713234586762d79c5a691785e9be418
https://git.kernel.org/stable/c/db1cafc77aaaf871509da06f4a864e9af6d6791f
Powered by blists - more mailing lists