Service interruption via invalid SMU SRAM ranges
Published Jan 10, 2023 · Updated Apr 7, 2025
Improper bounds checking in AMD EPYC 7002 and 7003 SMU firmware allows attackers to interrupt service via invalid SRAM ranges. The SMU accepts an out-of-range SRAM from/to address-space update because it does not validate the supplied bounds. AMD does not identify the interface or access prerequisites, or whether the resulting denial of service is a hang, crash, or reboot; no data exposure or modification is reported.
Summary
What happened
Improper bounds checking in AMD EPYC 7002 and 7003 SMU firmware allows attackers to interrupt service via invalid SRAM ranges. The SMU accepts an out-of-range SRAM from/to address-space update because it does not validate the supplied bounds. AMD does not identify the interface or access prerequisites, or whether the resulting denial of service is a hang, crash, or reboot; no data exposure or modification is reported.
The record
- CVE
- CVE-2023-20531
- Published
- Jan 10, 2023
- Updated
- Apr 7, 2025
- Vendor
- AMD
- Product
- AMD EPYC 7002 Series Processors
- Classifications
- CWE-119, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2023CVE publishedPublication date reported by the CVE source.
- Apr 7, 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