Critical Vulnerability in Linux Kernel: Driver Lock Issue in cpufreq AMD Pstate

linux Updated 02 Oct 2025

Summary

18/06/2025
N/A
No i
Unrated
Not published

CVE-2025-38038: 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. Affects linux versions 6.1.106-1 – 6.9.9-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Linux kernel is the core component of many operating systems, providing essential services for hardware and software interactions. It manages system resources, including CPU scheduling, memory management, and device control. The cpufreq subsystem is responsible for managing CPU frequency scaling, allowing the system to adjust the CPU's speed based on workload. This vulnerability affects the AMD Pstate driver, which is part of the cpufreq subsystem, potentially leading to system instability due to improper locking mechanisms.

Vulnerability Detail

The vulnerability arises from an unnecessary driver-wide lock in the set_boost function within the AMD Pstate driver. Since set_boost is a per-policy function call, the use of a global lock is excessive and can lead to deadlocks when combined with other mutex acquisitions in the mode-switch path of the status_store function. This can result in system hangs or crashes, impacting overall system performance and reliability.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. It is recommended to apply the patch as soon as it becomes available.

Conclusion

The CVE-2025-38038 vulnerability in the Linux kernel's AMD Pstate driver poses a significant risk due to potential deadlocks from unnecessary locking mechanisms. It is crucial to apply the available patches promptly to ensure system stability and security. Regular monitoring and updates are essential to protect against such vulnerabilities.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2025-38038 is a vulnerability in the Linux kernel's AMD Pstate driver that can lead to deadlocks due to unnecessary driver-wide locks.

This vulnerability can cause system hangs or crashes, affecting the stability and performance of your operating system.

Yes, a patch is available for Debian 13 in version 6.12.32-1. It is recommended to update to this version to mitigate the vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you cannot update immediately, ensure to monitor your system closely for any unusual behavior and plan for an update as soon as possible.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback