Service interruption via improper SMU resource locking
Published Jan 10, 2023 · Updated Apr 7, 2025
Improper input validation in AMD EPYC 7002 and 7003 SMU firmware allows attackers to interrupt service by locking resources. The SMU accepts an unspecified invalid input and improperly locks a resource, but AMD has not disclosed the input path or locking operation. CISA assesses network reachability without authentication; successful exploitation affects availability without reported data access or code execution.
Summary
What happened
Improper input validation in AMD EPYC 7002 and 7003 SMU firmware allows attackers to interrupt service by locking resources. The SMU accepts an unspecified invalid input and improperly locks a resource, but AMD has not disclosed the input path or locking operation. CISA assesses network reachability without authentication; successful exploitation affects availability without reported data access or code execution.
The record
- CVE
- CVE-2023-20532
- Published
- Jan 10, 2023
- Updated
- Apr 7, 2025
- Vendor
- AMD
- Product
- AMD EPYC 7002 Series Processors
- Classifications
- CWE-20, T1499
- 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?
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