Answer in brief
CVE-2025-38421 records a High severity (CVSS 7.8) vulnerability in platform/x86/amd: pmf: Use device managed allocations. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.14:-:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.14:rc7:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5b1122fc4995f308b21d7cfc64ef9880ac834d20 <0d10b532f861253c283863522d59d099fcb0796d || >=5b1122fc4995f308b21d7cfc64ef9880ac834d20 <d9db3a941270d92bbd1a6a6b54a10324484f2f2d || e70b4b8f93d7fcf8ee063a1d1f18782c4da3d335 || 3ed60e51ffdbfef14169bd967e21a6ba5e5ff42b || >=6.12.23 <6.13 || >=6.13.11 <6.14 | 0d10b532f861253c283863522d59d099fcb0796d, d9db3a941270d92bbd1a6a6b54a10324484f2f2d, 6.13, 6.14 |
| Linux/Linuxgeneric | 6.14 | Not reported |
| Linux/Linuxgeneric | >=e70b4b8f93d7fcf8ee063a1d1f18782c4da3d335 <d6a38e1a82d2f9abd0bae84a354654bccb8389f6 || >=5b1122fc4995f308b21d7cfc64ef9880ac834d20 <0d10b532f861253c283863522d59d099fcb0796d || >=5b1122fc4995f308b21d7cfc64ef9880ac834d20 <d9db3a941270d92bbd1a6a6b54a10324484f2f2d || 3ed60e51ffdbfef14169bd967e21a6ba5e5ff42b || >=6.12.23 <6.12.114 || >=6.13.11 <6.14 | d6a38e1a82d2f9abd0bae84a354654bccb8389f6, 0d10b532f861253c283863522d59d099fcb0796d, d9db3a941270d92bbd1a6a6b54a10324484f2f2d, 6.12.114, 6.14 |
Published upstream
Jul 25, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd: pmf: Use device managed allocations If setting up smart PC fails for any reason then this can lead to a double free when unloading amd-pmf. This is because dev->buf was freed but never set to NULL and is again freed in amd_pmf_remove(). To avoid subtle allocation bugs in failures leading to a double free change all allocations into device managed allocations.
Quoted source text, attributed separately from HOL analysis.