dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-29937

MEDIUM · 5.8 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 →
60/100
Remediation priority · Elevated
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 out of bounds read within the AMD Platform Management Framework (PMF) could allow an attacker to trigger a read of an arbitrary memory location potentially resulting in loss of availability or 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

An out-of-bounds read vulnerability in AMD Platform Management Framework (PMF) allows reading arbitrary memory locations, potentially exposing sensitive data or causing availability issues.

MitigationApply vendor-provided firmware/driver updates for AMD PMF when available; until then, limit exposure by restricting untrusted code execution and monitoring for anomalous memory access patterns.

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:P/PR:L/UI:N/VC:L/VI:N/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 presence
    Open Windows Device Manager, expand 'System devices' or 'Processors', and look for 'AMD Platform Management Framework' or similar AMD PMF-related drivers. Alternatively, check for the presence of 'amdpmf.sys' in C:\Windows\System32\drivers\
    Affected if The AMD PMF driver is found on the system
  2. Check AMD PMF driver version
    Right-click the AMD PMF driver in Device Manager, select Properties, go to the Driver tab, and note the Driver Version. Or right-click and select 'Properties' > 'Details' > 'Driver version'. If using PowerShell, run: Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.DeviceName -like '*PMF*'}
    Affected if The driver version cannot be determined or is earlier than the patched version (contact AMD for specific version numbers)
  3. Verify AMD PMF service status
    Open Services (services.msc), locate any AMD Platform Management Framework service, and check if it is Running or Stopped. Or via PowerShell: Get-Service | Where-Object {$_.Name -like '*pmf*' -or $_.DisplayName -like '*PMF*'}
    Affected if The AMD PMF service exists and is in a Running state
  4. Check for AMD PMF in installed programs
    Open Programs and Features (appwiz.cpl) or Settings > Apps, and search for 'AMD' or 'Platform Management Framework' in the installed software list. Also check the AMD Radeon Software installation for PMF components.
    Affected if AMD PMF software or related AMD utilities are installed
  5. Identify AMD chipset driver version
    Check the AMD chipset driver version as PMF often ships with it. In Device Manager, expand 'System devices' > 'AMD PSP' or 'AMD SMBus', check driver version. Or run: driverquery /v | findstr -i amdpmf
    Affected if AMD chipset drivers are installed with an older driver version that bundles the vulnerable PMF component

The system is likely affected if AMD Platform Management Framework driver or service is present and running, as this CVE affects the PMF component directly.

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 vendor-provided firmware/driver updates for AMD PMF when available; until then, limit exposure by restricting untrusted code execution and monitoring for anomalous memory access patterns.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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