Skip to main content
Mallory
HighVulnerability

CVE-2025-38421: Double Free in Linux Kernel AMD PMF Driver

Published Jul 25, 2025 · Updated 16 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.24%15th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Linux
IdentifiersCVE-2025-38421CWE-415 · Double Free

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.