Guest-memory overwrite via forged DIMM capacity metadata
Published Jun 10, 2026 · Updated Jun 10, 2026
Improper SPD validation in AMD EPYC 7003 and 9004 Series processors allows attackers to overwrite SEV-SNP guest memory. Firmware trusts DIMM-reported capacity without detecting that nonexistent physical addresses alias existing guest-memory locations, so host writes reach protected data. Reachability requires physical access, ring0 access with a non-compliant DIMM, or control of the BIOS-update Root of Trust; the bounded consequence is guest-data integrity loss.
Summary
What happened
Improper SPD validation in AMD EPYC 7003 and 9004 Series processors allows attackers to overwrite SEV-SNP guest memory. Firmware trusts DIMM-reported capacity without detecting that nonexistent physical addresses alias existing guest-memory locations, so host writes reach protected data. Reachability requires physical access, ring0 access with a non-compliant DIMM, or control of the BIOS-update Root of Trust; the bounded consequence is guest-data integrity loss.
The record
- CVE
- CVE-2024-21944
- Published
- Jun 10, 2026
- Updated
- Jun 10, 2026
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD EPYC™ 9004 Series Processors
- Classifications
- CWE-20, T1565
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 10, 2026CVE publishedPublication date reported by the CVE source.
- Jun 10, 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
- BadRAM proof-of-concept and end-to-end attacksfunctional · demonstrated
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