Integrity loss via SMU shared-memory overwrite
Published May 9, 2023 · Updated Jan 28, 2025
Out-of-bounds write in the SMU of 2nd and 3rd Gen AMD EPYC Processors allows attackers to corrupt shared memory. The SMU insufficiently validates an input before writing to a shared-memory buffer, allowing the write to pass the buffer's intended bounds. Exploitation requires privileged access, and AMD identifies the affected condition with SEV-SNP rather than SEV or SEV-ES.
Summary
What happened
Out-of-bounds write in the SMU of 2nd and 3rd Gen AMD EPYC Processors allows attackers to corrupt shared memory. The SMU insufficiently validates an input before writing to a shared-memory buffer, allowing the write to pass the buffer's intended bounds. Exploitation requires privileged access, and AMD identifies the affected condition with SEV-SNP rather than SEV or SEV-ES.
The record
- CVE
- CVE-2021-46763
- Published
- May 9, 2023
- Updated
- Jan 28, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- 3rd Gen AMD EPYC Processors
- Classifications
- CWE-787, T1565
- Attack vector
- Unavailable
- Privileges
- admin
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 28, 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.
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