Denial of service via PCIE bounds check
Published May 11, 2022 · Updated Sep 16, 2024
Insufficient bounds checking in AMD Ryzen Processors of various versions allows local authenticated users to cause denial of service through the SMU PCIE Hot Plug Config Table. The SMU table accepts out-of-range values and accesses invalid address space, which can stop processor service. The same condition is reported for AMD EPYC and Athlon processor families; exploitation requires local authenticated access to the relevant platform interface and can interrupt availability without reported confidentiality or integrity impact.
Summary
What happened
Insufficient bounds checking in AMD Ryzen Processors of various versions allows local authenticated users to cause denial of service through the SMU PCIE Hot Plug Config Table. The SMU table accepts out-of-range values and accesses invalid address space, which can stop processor service. The same condition is reported for AMD EPYC and Athlon processor families; exploitation requires local authenticated access to the relevant platform interface and can interrupt availability without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2021-26372
- Published
- May 11, 2022
- Updated
- Sep 16, 2024
- Vendor
- AMD
- Product
- AMD EPYC Processors
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 11, 2022CVE 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