System crash via NULL log-file output
Published Sep 6, 2025 · Updated Sep 8, 2025
NULL pointer dereference in AMD Crash Defender allows local users to crash affected AMD systems by writing a NULL output to a log file. AMD has not disclosed the responsible function or input path; the published mechanism states only that Crash Defender dereferences a NULL pointer while writing log output. Low-privileged local access is required, and successful exploitation interrupts system availability without reported confidentiality or integrity impact.
Summary
What happened
NULL pointer dereference in AMD Crash Defender allows local users to crash affected AMD systems by writing a NULL output to a log file. AMD has not disclosed the responsible function or input path; the published mechanism states only that Crash Defender dereferences a NULL pointer while writing log output. Low-privileged local access is required, and successful exploitation interrupts system availability without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2025-0009
- Published
- Sep 6, 2025
- Updated
- Sep 8, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen™ 7000 Series Desktop Processors
- Classifications
- CWE-476, T1529
- 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?
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.
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