Arbitrary code execution via signed APCB corruption
Published Aug 13, 2024 · Updated Mar 18, 2025
Out-of-bounds write in AMD PSP1 APCB processing allows local users to execute arbitrary code through a modified, signed BIOS image. The PSP1 firmware writes beyond the APCB buffer while processing attacker-controlled configuration data embedded in the BIOS image. Exploitation requires high privileges, user interaction, BIOS-image modification, and a valid signature, and successful execution can compromise platform confidentiality, integrity, and availability.
Summary
What happened
Out-of-bounds write in AMD PSP1 APCB processing allows local users to execute arbitrary code through a modified, signed BIOS image. The PSP1 firmware writes beyond the APCB buffer while processing attacker-controlled configuration data embedded in the BIOS image. Exploitation requires high privileges, user interaction, BIOS-image modification, and a valid signature, and successful execution can compromise platform confidentiality, integrity, and availability.
The record
- CVE
- CVE-2021-26344
- Published
- Aug 13, 2024
- Updated
- Mar 18, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen™ Embedded V1000 Series Processors
- Classifications
- CWE-787, T1542.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 13, 2024CVE publishedPublication date reported by the CVE source.
- Mar 18, 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=v
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.
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