Guest-memory corruption via undisclosed SEV-ES TMR bug
Published May 10, 2022 · Updated Sep 16, 2024
Memory-integrity failure in AMD 3rd Gen EPYC before MilanPI-SP3_1.0.0.4 allows local users to corrupt SNP-active VM memory. AMD has not disclosed the specific SEV-ES TMR operation that mishandles memory or the triggering input. Low-privilege local access and an SNP-active virtual machine are required; the bounded consequence is loss of guest-memory integrity.
Summary
What happened
Memory-integrity failure in AMD 3rd Gen EPYC before MilanPI-SP3_1.0.0.4 allows local users to corrupt SNP-active VM memory. AMD has not disclosed the specific SEV-ES TMR operation that mishandles memory or the triggering input. Low-privilege local access and an SNP-active virtual machine are required; the bounded consequence is loss of guest-memory integrity.
The record
- CVE
- CVE-2021-26324
- Published
- May 10, 2022
- Updated
- Sep 16, 2024
- Vendor
- Advanced Micro Devices, Inc.
- Product
- 3rd Gen AMD EPYC Processors
- Classifications
- T1565
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 10, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=unspecified <MilanPI-SP3_1.0.0.4
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