Instruction-integrity loss via incomplete microcode cleanup
Published Sep 6, 2025 · Updated Feb 26, 2026
Improper cleanup in AMD CPU microcode patch loading allows local administrators on affected processors to corrupt x86 instruction execution. AMD identifies the locus as CPU microcode patch loading but has not disclosed which state remains uncleared or how that residue permits malicious microcode to load. Exploitation requires local administrator privileges; successful loading undermines instruction integrity without a reported availability impact.
Summary
What happened
Improper cleanup in AMD CPU microcode patch loading allows local administrators on affected processors to corrupt x86 instruction execution. AMD identifies the locus as CPU microcode patch loading but has not disclosed which state remains uncleared or how that residue permits malicious microcode to load. Exploitation requires local administrator privileges; successful loading undermines instruction integrity without a reported availability impact.
The record
- CVE
- CVE-2025-0032
- Published
- Sep 6, 2025
- Updated
- Feb 26, 2026
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen Threadripper 9000 Processors
- Classifications
- CWE-459, T1601.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 6, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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.
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