dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-52540

HIGH · 8.5 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 →
87/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
An improper input validation vulnerability within the AMD Platform Management Framework (PMF) Driver can allow a local attacker to write Out-of-Bounds, potentially resulting in privilege escalation.

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

A local privilege escalation vulnerability exists in the AMD Platform Management Framework (PMF) driver due to improper input validation. The flaw allows a local attacker to perform out-of-bounds memory writes, potentially elevating privileges to execute code at a higher privilege level.

MitigationApply the AMD-provided driver update for the PMF framework once released. Until the patch is available, restrict local access to trusted users only and monitor for any suspicious interaction with the PMF driver.

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:H/VI:H/VA:H/SC:N/SI:N/SA:N/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. Verify AMD PMF driver is present
    Check for the presence of AmdPMF.sys in the System32\drivers folder or query installed drivers using 'driverquery /v | findstr -i pmf'
    Affected if The AMD PMF driver is not installed on the system (not affected)
  2. Retrieve driver file version
    Right-click AmdPMF.sys and select Properties > Details, or run 'wmic datafile where "name='C:\\Windows\\System32\\drivers\\AmdPMF.sys'" get Version'
    Affected if Driver version exists and is within the affected version range (need to compare against fixed version once released)
  3. Confirm driver is loaded
    Run 'sc query AmdPMF' or check Device Manager for AMD PMF device under System devices
    Affected if Driver service is running or set to auto-start (driver is active and vulnerability is exploitable)
  4. Check driver service configuration
    Run 'sc qc AmdPMF' to view service start type and binary path
    Affected if Service is present and configured to run (even if currently stopped, the vulnerable binary exists)
  5. Review system event logs for PMF driver errors
    Open Event Viewer > Windows Logs > System and filter for source 'AmdPMF' or Event ID related to driver load failures
    Affected if AMD PMF driver events are present (confirms driver is in use)

System is affected if AMD PMF driver is present and the installed version falls within the vulnerable range; once AMD releases the fix, compare your version to the patched version to confirm remediation.

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 the AMD-provided driver update for the PMF framework once released. Until the patch is available, restrict local access to trusted users only and monitor for any suspicious interaction with the PMF driver.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52540 — 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-52540 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