Service interruption via SMU message-port address race
Published May 11, 2022 · Updated Sep 16, 2024
A TOCTOU race condition in the AMD EPYC SMU allows local users to interrupt service by manipulating a message port register address. The SMU permits the caller to obtain and alter that register address between the check and subsequent use, so the operation targets a changed address. Low-privileged local access and winning the race are required; AMD reports denial of service but does not identify whether the system hangs, crashes, or reboots.
Summary
What happened
A TOCTOU race condition in the AMD EPYC SMU allows local users to interrupt service by manipulating a message port register address. The SMU permits the caller to obtain and alter that register address between the check and subsequent use, so the operation targets a changed address. Low-privileged local access and winning the race are required; AMD reports denial of service but does not identify whether the system hangs, crashes, or reboots.
The record
- CVE
- CVE-2021-26350
- Published
- May 11, 2022
- Updated
- Sep 16, 2024
- Vendor
- AMD
- Product
- AMD EPYC Processors
- Classifications
- CWE-367, CAPEC-29, 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