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

CVE-2025-29935

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
An out of bounds write within the AMD Platform Management Framework (PMF) could allow an attacker to execute arbitrary code at an elevated privilege level potentially leading to loss of confidentiality integrity, or availability.

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

CVE-2025-29935 is an out-of-bounds write vulnerability in AMD's Platform Management Framework (PMF), a system-level component. The vulnerability allows an attacker to execute arbitrary code at elevated privilege levels due to improper bounds checking when writing to memory, potentially compromising confidentiality, integrity, and availability.

MitigationApply vendor-supplied patches or firmware updates for AMD Platform Management Framework. Given the elevated privilege execution path, prioritize patching systems with direct hardware access or those in privileged network positions.

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. Identify if AMD PMF is present
    Check system for AMD Platform Management Framework installation. On Windows, look in Programs and Features or check C:\Program Files\AMD\PMF. On Linux, check /usr/lib/amd-pmf or via package manager: dpkg -l | grep -i amd-pmf or rpm -qa | grep -i amd-pmf.
    Affected if AMD PMF software is not installed on the system
  2. Locate PMF driver or service
    Check for PMF-related drivers or services. On Windows, run 'sc query' or check Device Manager for AMD PMF devices. On Linux, check lsmod | grep pmf or systemctl list-units --type=service --all | grep -i pmf.
    Affected if AMD PMF driver or service is running on the system
  3. Determine PMF version
    If AMD PMF is found, determine its version. On Windows, right-click the executable in Program Files and select Properties > Details for version info. On Linux, run 'modinfo pmf' or check the installed package version.
    Affected if The installed version falls within the affected range (version information cannot be verified without vendor reference)
  4. Check firmware version
    Since PMF is a system-level component, check BIOS/UEFI firmware for PMF-related updates. Access BIOS setup during boot and look for PMF or Platform Management Framework version under the BIOS version information, or use tools like 'dmidecode' on Linux if available.
    Affected if The system firmware PMF component version is outdated or unknown

A system is likely affected if AMD Platform Management Framework is installed and the version cannot be confirmed as patched by AMD.

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-supplied patches or firmware updates for AMD Platform Management Framework. Given the elevated privilege execution path, prioritize patching systems with direct hardware access or those in privileged network positions.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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