CVE-2025-38421: Double Free in Linux Kernel AMD PMF Driver
- Vendor
- Linux
CVE-2025-38421 is a double-free vulnerability in the Linux kernel's AMD Platform Management Framework (amd-pmf) driver. If Smart PC setup fails, error handling frees dev->buf without setting the pointer to NULL. Subsequent driver removal causes amd_pmf_remove() to free the same buffer again, potentially corrupting kernel memory and crashing the system. The fix replaces the affected allocations with device-managed allocations.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
The double free can corrupt kernel memory and cause a kernel crash or denial of service. SUSE assesses local exploitation with low privileges as potentially affecting confidentiality, integrity, and availability, but arbitrary code execution and privilege escalation are not established by the vulnerability-specific technical details.
Mitigation
If you can’t patch tonight, do this now.
Apply vendor kernel security updates for affected systems. No specific temporary workaround or configuration-based mitigation is identified in the available information.
Remediation
Patch, then assume compromise.
Install a vendor-supported kernel update containing the fix titled "platform/x86/amd: pmf: Use device managed allocations" and reboot into the updated kernel. Debian stable (trixie) fixes the issue in linux package version 6.12.115-2. For affected SUSE products, install the applicable security-fixed kernel packages; version 6.12.0-160000.6.1 is identified as a fixed version for relevant products. Ubuntu users should install the applicable kernel security updates. Fixed versions vary by distribution and product.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-38421 exploited in the wild?
- Yes. As of Nov 2, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2025-38421?
- As of Nov 2, 2026, Mallory has found no public exploit for CVE-2025-38421.
- Is there a patch for CVE-2025-38421?
- Install a vendor-supported kernel update containing the fix titled "platform/x86/amd: pmf: Use device managed allocations" and reboot into the updated kernel. Debian stable (trixie) fixes the issue in linux package version 6.12.115-2.
- What products are affected by CVE-2025-38421?
- Linux Kernel.
- How severe is CVE-2025-38421?
- CVE-2025-38421 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.24% (15th percentile) as of Nov 2, 2026.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.