Local service interruption via driver buffer overflow
Published May 15, 2026 · Updated May 15, 2026
Improper input validation in AMD Secure Processor PCI drivers allows local users to trigger a buffer overflow and crash an affected system. AMD identifies the ASP PCI driver as the vulnerable locus but does not disclose the specific request, function, or unchecked buffer operation. Low-privileged local access to a Windows system with an affected driver is required; successful exploitation interrupts the system and can alter limited data.
Summary
What happened
Improper input validation in AMD Secure Processor PCI drivers allows local users to trigger a buffer overflow and crash an affected system. AMD identifies the ASP PCI driver as the vulnerable locus but does not disclose the specific request, function, or unchecked buffer operation. Low-privileged local access to a Windows system with an affected driver is required; successful exploitation interrupts the system and can alter limited data.
The record
- CVE
- CVE-2025-0045
- Published
- May 15, 2026
- Updated
- May 15, 2026
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen™ 7000 Series Desktop Processors
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 15, 2026CVE publishedPublication date reported by the CVE source.
- May 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo