Physical memory disclosure via unvalidated bootloader syscall
Published May 9, 2023 · Updated Jan 27, 2025
Improper syscall input validation in AMD TEE on affected Ryzen and Athlon processors allows physically proximate attackers to expose ASP memory. The bootloader accepts input from an attacker-controlled Uapp without adequate validation and sends bootloader-accessible ASP memory to a serial port. Exploitation requires physical access, control of a Uapp executing under the bootloader, and access to the resulting serial output.
Summary
What happened
Improper syscall input validation in AMD TEE on affected Ryzen and Athlon processors allows physically proximate attackers to expose ASP memory. The bootloader accepts input from an attacker-controlled Uapp without adequate validation and sends bootloader-accessible ASP memory to a serial port. Exploitation requires physical access, control of a Uapp executing under the bootloader, and access to the resulting serial output.
The record
- CVE
- CVE-2021-46759
- Published
- May 9, 2023
- Updated
- Jan 27, 2025
- Vendor
- AMD
- Product
- Ryzen 5000 Series Mobile Processors with Radeon Graphics (Lucienne)
- Classifications
- CWE-787, T1052
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 27, 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?
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.
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