SMU hang via insufficient bounds checking
Published Nov 16, 2021 · Updated Sep 16, 2024
Improper bounds checking in SMU firmware for AMD Ryzen and Athlon Series allows local users to hang the SMU via invalid memory access. The SMU accepts an out-of-range value without adequate validation and performs an invalid memory access or update that stops request processing. Low-privileged local access is required; the hang prevents the SMU from servicing further requests from other platform components.
Summary
What happened
Improper bounds checking in SMU firmware for AMD Ryzen and Athlon Series allows local users to hang the SMU via invalid memory access. The SMU accepts an out-of-range value without adequate validation and performs an invalid memory access or update that stops request processing. Low-privileged local access is required; the hang prevents the SMU from servicing further requests from other platform components.
The record
- CVE
- CVE-2021-26336
- Published
- Nov 16, 2021
- Updated
- Sep 16, 2024
- Vendor
- AMD
- Product
- AMD Ryzen Series
- Classifications
- CWE-119, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 16, 2021CVE 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=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