Memory integrity loss via unchecked ASP syscall
Published May 9, 2023 · Updated Jan 28, 2025
Memory corruption in the Secure Processor of affected AMD processors allows local users to zero arbitrary memory through a crafted system call. The ASP performs insufficient bounds checking on a system call issued from a compromised AMD bootloader, allowing attacker-selected memory values to be initialized to zero. Exploitation requires low local privileges and control of the AMD bootloader, and the documented consequence is loss of memory integrity.
Summary
What happened
Memory corruption in the Secure Processor of affected AMD processors allows local users to zero arbitrary memory through a crafted system call. The ASP performs insufficient bounds checking on a system call issued from a compromised AMD bootloader, allowing attacker-selected memory values to be initialized to zero. Exploitation requires low local privileges and control of the AMD bootloader, and the documented consequence is loss of memory integrity.
The record
- CVE
- CVE-2021-26354
- Published
- May 9, 2023
- Updated
- Jan 28, 2025
- Vendor
- AMD
- Product
- Ryzen 5000 Series Mobile Processors with Radeon Graphics (Lucienne)
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 28, 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.
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