Privileged denial of service via cross-process unmapping
Published May 12, 2022 · Updated Sep 16, 2024
Process-type validation failure in AMD Ryzen and Athlon firmware allows privileged local users to cause a service interruption. Trusted OS does not sufficiently verify a caller's process type before allowing a lower-privileged process to unmap memory owned by a higher-privileged process. Exploitation requires high local privileges and denies service by invalidating memory belonging to a more privileged Trusted OS process.
Summary
What happened
Process-type validation failure in AMD Ryzen and Athlon firmware allows privileged local users to cause a service interruption. Trusted OS does not sufficiently verify a caller's process type before allowing a lower-privileged process to unmap memory owned by a higher-privileged process. Exploitation requires high local privileges and denies service by invalidating memory belonging to a more privileged Trusted OS process.
The record
- CVE
- CVE-2021-26368
- Published
- May 12, 2022
- Updated
- Sep 16, 2024
- Vendor
- AMD
- Product
- AMD Ryzen Series
- Classifications
- CWE-345, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 12, 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