[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025030707-CVE-2025-21841-1182@gregkh>
Date: Fri, 7 Mar 2025 10:10:11 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-21841: cpufreq/amd-pstate: Fix cpufreq_policy ref counting
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
cpufreq/amd-pstate: Fix cpufreq_policy ref counting
amd_pstate_update_limits() takes a cpufreq_policy reference but doesn't
decrement the refcount in one of the exit paths, fix that.
The Linux kernel CVE team has assigned CVE-2025-21841 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 45722e777fd99ea863fe653c1838d39f678506e2 and fixed in 6.12.16 with commit 56e6976793c0fcf1638aa534242408ab4e4ca705
Issue introduced in 6.12 with commit 45722e777fd99ea863fe653c1838d39f678506e2 and fixed in 6.13.4 with commit 28e4c515cf644c621800bd97841757fd49891ba4
Issue introduced in 6.12 with commit 45722e777fd99ea863fe653c1838d39f678506e2 and fixed in 6.14-rc2 with commit 3ace20038e19f23fe73259513f1f08d4bf1a3c83
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-21841
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/56e6976793c0fcf1638aa534242408ab4e4ca705
https://git.kernel.org/stable/c/28e4c515cf644c621800bd97841757fd49891ba4
https://git.kernel.org/stable/c/3ace20038e19f23fe73259513f1f08d4bf1a3c83
Powered by blists - more mailing lists