dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2025-48515

MEDIUM · 5.4 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 →
54/100
Remediation priority · Moderate

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
Insufficient parameter sanitization in AMD Secure Processor (ASP) Boot Loader could allow an attacker with access to SPIROM upgrade to overwrite the memory, potentially resulting in 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

This vulnerability exists in the AMD Secure Processor (ASP) Boot Loader firmware where insufficient parameter sanitization allows an attacker with SPIROM upgrade access to overwrite memory contents. The attack enables potential arbitrary code execution at the firmware level, which could compromise the entire platform's security chain.

MitigationApply the AMD firmware patch when released; restrict physical and privileged access to SPIROM upgrade mechanisms until the update is applied.

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
Physical
Complexity
High
Privileges
High
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:P/AC:H/AT:N/PR:H/UI:P/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. Identify AMD Secure Processor presence
    On Windows, run 'msinfo32' and check for 'AMD Secure Processor' under 'Security' or 'Hardware Abstraction'. On Linux, run 'lspci | grep -i amd' or check /dev/tpm* devices. Some AMD systems list it in UEFI/BIOS setup under 'Security' or 'PSP' settings.
    Affected if The system has an AMD Secure Processor (PSP) component present
  2. Locate ASP Boot Loader firmware version
    Access the UEFI/BIOS setup (restart, press Del/F2/F10 during boot). Navigate to Security or Advanced settings. Look for 'AMD Secure Processor', 'PSP', or 'Boot Loader' version entries. Alternatively, on Linux, try 'cat /sys/devices/system/cpu/cpu0/ microcode/version' or check AMD's PSP firmware tools if available.
    Affected if Unable to locate or confirm the ASP Boot Loader firmware version (unknown version status)
  3. Determine SPIROM upgrade interface exposure
    Check if SPIROM/BIOS chip upgrade mechanisms are exposed: On Linux, check 'ls -la /dev/mtd*' or 'ls -la /dev/spi*'. In UEFI/BIOS, look for 'BIOS Update', 'SPI Update', or 'Flasher' options under Security settings. Review system documentation for firmware update procedures that use SPIROM.
    Affected if SPIROM upgrade interface is accessible or enabled (USB flashing, BIOS update enabled without authentication, or debug/development modes active)
  4. Assess physical and privileged access risk
    Review who has physical access to the system (chassis, motherboard jumper settings for firmware flash enable). Check if unprivileged users or services can trigger firmware updates. In enterprise environments, verify if management interfaces (BIOS setup, TPM management tools) are password-protected or restricted.
    Affected if Physical access is unrestricted or privileged access controls on firmware update are weak or missing

A system is affected if it contains an AMD Secure Processor with Boot Loader firmware for which the version is either unconfirmed or falls within the unpatched range, and the SPIROM upgrade interface is accessible to an attacker with physical or privileged access.

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 firmware patch when released; restrict physical and privileged access to SPIROM upgrade mechanisms until the update is applied.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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