TEE OS crash via TOCTOU out-of-bounds read
Published Jan 10, 2023 · Updated Apr 9, 2025
TOCTOU in AMD Ryzen 3000 and 5000 Series Processors allows local users to crash the TEE OS through a compromised BIOS. The TEE OS checks a BIOS-controlled memory resource, then uses it after its state changes and reads beyond the intended bounds. Reaching the flaw requires low-privileged local access and prior BIOS compromise; the documented consequence is a service-interrupting TEE OS crash.
Summary
What happened
TOCTOU in AMD Ryzen 3000 and 5000 Series Processors allows local users to crash the TEE OS through a compromised BIOS. The TEE OS checks a BIOS-controlled memory resource, then uses it after its state changes and reads beyond the intended bounds. Reaching the flaw requires low-privileged local access and prior BIOS compromise; the documented consequence is a service-interrupting TEE OS crash.
The record
- CVE
- CVE-2021-46795
- Published
- Jan 10, 2023
- Updated
- Apr 9, 2025
- Vendor
- AMD
- Product
- AMD Ryzen 5000 Series Processors
- Classifications
- CWE-367, CAPEC-29, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 10, 2023CVE publishedPublication date reported by the CVE source.
- Apr 9, 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.
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