dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2025-0045

MEDIUM · 6.9 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 →
71/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
Improper Input validation in the AMD Secure Processor (ASP) PCI driver may allow a local attacker to create a buffer overflow condition, potentially resulting in a crash or denial of service

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

Improper input validation in the AMD Secure Processor (ASP) PCI driver allows a local attacker to trigger a buffer overflow condition. This vulnerability exists in the driver's handling of input data received through the PCI interface, potentially leading to memory corruption, system crashes, or denial of service.

MitigationApply the AMD-provided driver/firmware patch for the Secure Processor when available. Until then, limit local access to trusted users and monitor for unusual system behavior related to the ASP 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:N/VI:L/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 hardware presence
    Check system hardware information using 'lspci' or checking BIOS/UEFI settings for AMD Secure Processor. On Windows, use 'wmic baseboard get product,manufacturer' or check Device Manager under System devices for AMD Secure Processor entries.
    Affected if The system has AMD Secure Processor hardware and the vulnerability can apply.
  2. Verify AMD Secure Processor PCI driver is loaded
    On Linux, run 'lsmod | grep asp' or check '/proc/modules' for asp_* modules. On Windows, check Device Manager for AMD Secure Processor drivers or use 'driverquery' to list loaded drivers.
    Affected if The ASP PCI driver is loaded or installed on the system.
  3. Check driver/firmware version
    On Linux, use 'modinfo amd_sp' or similar module names. On Windows, right-click the AMD Secure Processor driver in Device Manager, select Properties, and check the Driver Version field. Compare against any official AMD advisories listing fixed versions.
    Affected if The installed driver version matches or predates versions listed as vulnerable in AMD security advisories.
  4. Review system logs for ASP driver anomalies
    Check /var/log/messages, /var/log/syslog, or use 'journalctl -xe' on Linux. On Windows, check Event Viewer under Windows Logs > System for Event ID 1001 (Bugcheck) or driver-related errors mentioning amd_sp, ASP, or Secure Processor.
    Affected if Recent crashes, memory corruption errors, or bugcheck events reference the ASP PCI driver.
  5. Verify PCI interface exposure
    Confirm the ASP driver is exposed to PCI interface input. Use 'lspci -v' to list the AMD Secure Processor PCI device and verify the driver is bound to it. Check if the PCI device is accessible to untrusted local users.
    Affected if The ASP PCI device is present and accessible to local users beyond trusted administrators.

A system is affected if it has AMD Secure Processor hardware with the ASP PCI driver loaded, where the driver version is within the vulnerable range or system logs show ASP-related crashes, and local untrusted users can interact with the PCI interface.

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/firmware patch for the Secure Processor when available. Until then, limit local access to trusted users and monitor for unusual system behavior related to the ASP driver.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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