Database/Control plane, storage & DevOps
Linux cpufreq/amd-pstate - cpufreq_policy reference counting: amd_pstate_update_limits() takes a cpufreq_policy
CVE-2025-21841Control plane, storage & DevOpscurated
Impact
amd_pstate_update_limits() takes a cpufreq_policy reference and never drops it. A leaked reference means the policy object can never be freed, so CPU hotplug and driver unbind hang or leak indefinitely - the sort of defect that makes a node impossible to cleanly reconfigure without a reboot.
Who can reach it
Local, through the amd-pstate limits-update path.
What to do
Distro kernel update plus reboot.
References
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.