CVE-2025-38421
BaseFortify
Publication date: 2025-07-25
Last updated on: 2025-11-19
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.14 |
| linux | linux_kernel | 6.14 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-415 | The product calls free() twice on the same memory address. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a double free issue in the Linux kernel's amd-pmf component on x86 AMD platforms. If setting up the smart PC fails, the device buffer (dev->buf) is freed but not set to NULL, leading to it being freed again during the removal process (amd_pmf_remove()). This can cause subtle allocation bugs and potential instability. The fix involved changing all allocations to device managed allocations to prevent double free errors.
How can this vulnerability impact me? :
The double free vulnerability can lead to memory corruption, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges on affected systems running the vulnerable Linux kernel component.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the fix has been applied, which changes all allocations into device managed allocations to prevent double free errors in amd-pmf. Avoid using vulnerable kernel versions and apply vendor patches as soon as they are available.