Local memory corruption via graphics-driver buffer overflow
Published Sep 6, 2025 · Updated Sep 8, 2025
Out-of-bounds write in the AMD Linux graphics driver allows local users to corrupt memory through a driver buffer overflow. AMD has not disclosed the affected function or input path; the driver writes beyond a buffer boundary while processing attacker-controlled data. Exploitation requires local low-privileged access, and published assessments disagree on whether user interaction is required; consequences are limited to memory confidentiality, integrity, and availability.
Summary
What happened
Out-of-bounds write in the AMD Linux graphics driver allows local users to corrupt memory through a driver buffer overflow. AMD has not disclosed the affected function or input path; the driver writes beyond a buffer boundary while processing attacker-controlled data. Exploitation requires local low-privileged access, and published assessments disagree on whether user interaction is required; consequences are limited to memory confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-0010
- Published
- Sep 6, 2025
- Updated
- Sep 8, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen™ 7000 Series Desktop Processors
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 6, 2025CVE publishedPublication date reported by the CVE source.
- Sep 8, 2025Record 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