dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-29936

HIGH · 8.4 CVSS v4.0 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper input validation within the AMD Platform Management Framework (PMF) could allow an attacker to unmap arbitrary memory pages potentially impacting integrity and availability, or allowing privilege escalation resulting in loss of confidentiality.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper input validation in AMD Platform Management Framework (PMF) allows an attacker to unmap arbitrary memory pages, enabling potential integrity and availability compromise or privilege escalation for confidentiality loss. This is a kernel-level driver vulnerability in AMD systems.

MitigationApply AMD-provided firmware/driver patches for PMF when released; prior to patch, minimize attack surface by restricting local privileged access and monitoring for anomalous memory manipulation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm AMD hardware is present
    Check system information for AMD processor or chipset. On Windows: 'systeminfo' or 'msinfo32'. On Linux: 'lscpu | grep -i amd' or 'dmidecode -s system-manufacturer'.
    Affected if System does not have AMD hardware - not affected. If AMD hardware present, continue to next check.
  2. Identify if AMD PMF driver is installed
    On Windows: Check Device Manager under 'System devices' for 'AMD Platform Management Framework' or run 'driverquery /v | findstr -i pmf'. On Linux: Check for 'amd_pmf' module via 'lsmod | grep -i pmf' or check /dev for PMF-related entries.
    Affected if AMD PMF driver not installed - not affected. If driver is present, continue to next check.
  3. Check AMD PMF driver version
    On Windows: Right-click the AMD PMF device in Device Manager > Properties > Driver tab to view version. On Linux: Check driver version via 'modinfo amd_pmf' if module is loaded.
    Affected if Unable to determine version - assume potentially affected and verify with AMD advisory. Compare your version to AMD's official vulnerability disclosure for CVE-2025-29936.
  4. Verify PMF service is running and enabled
    On Windows: Check Services (services.msc) for 'AMD PMF' service or via 'sc query amd_pmf'. On Linux: Check systemctl status for PMF-related services if applicable.
    Affected if PMF service is disabled or not running - lower risk but driver may still load on demand. Review system logs for PMF driver load events.
  5. Review memory management audit logs
    Check Windows Event Viewer under Security/System logs for unexpected memory unmap operations, or use 'bcdedit /debug on' if kernel debugging is enabled. On Linux: Review dmesg for 'unmap' or 'remap' operations from amd_pmf.
    Affected if Unusual memory manipulation events present - may indicate exploitation attempts or vulnerable configuration.

System is affected if it has AMD hardware with the AMD PMF driver installed and the driver version falls within the vulnerable range specified in AMD's official advisory for CVE-2025-29936; the PMF service being enabled increases exposure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply AMD-provided firmware/driver patches for PMF when released; prior to patch, minimize attack surface by restricting local privileged access and monitoring for anomalous memory manipulation.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29936 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data