Secure Processor code execution via SYS_KEY_DERIVE
Published Jan 10, 2023 · Updated Apr 9, 2025
Out-of-bounds write in AMD EPYC 7001, 7002, and 7003 processors allows local users to execute code in the Secure Processor. The SYS_KEY_DERIVE system call insufficiently validates input from a compromised user application or ABL, allowing writes that corrupt ASP OS memory. A local user application or ABL must already be compromised; successful exploitation crosses into the isolated processor and can execute arbitrary code there.
Summary
What happened
Out-of-bounds write in AMD EPYC 7001, 7002, and 7003 processors allows local users to execute code in the Secure Processor. The SYS_KEY_DERIVE system call insufficiently validates input from a compromised user application or ABL, allowing writes that corrupt ASP OS memory. A local user application or ABL must already be compromised; successful exploitation crosses into the isolated processor and can execute arbitrary code there.
The record
- CVE
- CVE-2021-26398
- Published
- Jan 10, 2023
- Updated
- Apr 9, 2025
- Vendor
- AMD
- Product
- AMD EPYC 7002 Series Processors
- Classifications
- CWE-787, T1068
- 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.
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