CVE-2025-38038
Description
A flaw was found in the Linux kernel. A local user could trigger a deadlock in the cpufreq: amd-pstate driver. This occurs when a lock intended for per-policy function calls conflicts with another lock during a mode-switch operation. This vulnerability can lead to a system hang, resulting in a Denial of Service (DoS).
Mitigation
To mitigate this issue, the `amd-pstate` kernel module can be prevented from loading. This may impact CPU frequency scaling and power management on systems with AMD processors.
To blacklist the module, create a file named `/etc/modprobe.d/blacklist-amd-pstate.conf` with the following content:
`blacklist amd-pstate`
After creating the file, regenerate the initramfs and reboot the system for the changes to take effect.
`dracut -f -v`
A system reboot is required for the blacklist to be fully applied.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | 5.5 | N/A |
| Attack Vector | Local | Local | N/A |
| Attack Complexity | Low | Low | N/A |
| Privileges Required | Low | Low | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | None | None | N/A |
| Integrity Impact | None | None | N/A |
| Availability Impact | High | High | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart
Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
