Service interruption via unchecked DRAM addresses
Published May 9, 2023 · Updated Jan 28, 2025
Out-of-bounds write in the SMU on AMD 2nd and 3rd Gen EPYC processors allows attackers to deny service by corrupting ASP memory. The System Management Unit fails to validate supplied DRAM addresses before using them for writes, permitting sensitive AMD Secure Processor memory to be overwritten. AMD has not published the access conditions or exact form of service interruption produced by successful corruption.
Summary
What happened
Out-of-bounds write in the SMU on AMD 2nd and 3rd Gen EPYC processors allows attackers to deny service by corrupting ASP memory. The System Management Unit fails to validate supplied DRAM addresses before using them for writes, permitting sensitive AMD Secure Processor memory to be overwritten. AMD has not published the access conditions or exact form of service interruption produced by successful corruption.
The record
- CVE
- CVE-2021-46764
- Published
- May 9, 2023
- Updated
- Jan 28, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- 3rd Gen AMD EPYC Processors
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
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?
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