Windows crash via unvalidated system process ID
Published Feb 12, 2025 · Updated Sep 23, 2025
Improper input validation in AMD Crash Defender allows local users to crash Windows by supplying a system process ID to its kernel driver. The kernel-mode driver fails to reject a caller-supplied Windows system process ID, and processing that identifier crashes the operating system. Local low-privileged access is required; successful exploitation interrupts the host without reported confidentiality or integrity impact.
Summary
What happened
Improper input validation in AMD Crash Defender allows local users to crash Windows by supplying a system process ID to its kernel driver. The kernel-mode driver fails to reject a caller-supplied Windows system process ID, and processing that identifier crashes the operating system. Local low-privileged access is required; successful exploitation interrupts the host without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2024-21971
- Published
- Feb 12, 2025
- Updated
- Sep 23, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen™ 7000 Series Desktop Processors
- Classifications
- CWE-1220, T1529
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2025CVE publishedPublication date reported by the CVE source.
- Sep 23, 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