SNP memory corruption via unchecked RMP bounds
Published Jan 10, 2023 · Updated Apr 9, 2025
Memory corruption in SEV-ES on 3rd Gen AMD EPYC processors allows local users to corrupt the RMP and undermine SNP memory integrity. The affected SEV-ES path fails to constrain a memory operation to the Reverse Map Table's bounds, permitting corruption of protected SNP metadata. Exploitation requires local low-privileged access; AMD has not disclosed the affected function or input.
Summary
What happened
Memory corruption in SEV-ES on 3rd Gen AMD EPYC processors allows local users to corrupt the RMP and undermine SNP memory integrity. The affected SEV-ES path fails to constrain a memory operation to the Reverse Map Table's bounds, permitting corruption of protected SNP metadata. Exploitation requires local low-privileged access; AMD has not disclosed the affected function or input.
The record
- CVE
- CVE-2021-26409
- Published
- Jan 10, 2023
- Updated
- Apr 9, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- 3rd Gen AMD EPYC Processors
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 10, 2023CVE publishedPublication date reported by the CVE source.
- Apr 9, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=various
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.
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