Memory corruption via insufficient ECC syscall validation
Published Jan 10, 2023 · Updated Apr 9, 2025
Memory corruption in AMD EPYC 7001, 7002, and 7003 AGESA firmware allows local users to corrupt AMD Secure Processor OS memory. The SVC_ECC_PRIMITIVE system call inadequately validates input from a compromised user application or ABL before operating on ASP OS memory. Access through a compromised ASP user application or ABL is required; successful exploitation compromises firmware-memory integrity and can interrupt secure-processor services.
Summary
What happened
Memory corruption in AMD EPYC 7001, 7002, and 7003 AGESA firmware allows local users to corrupt AMD Secure Processor OS memory. The SVC_ECC_PRIMITIVE system call inadequately validates input from a compromised user application or ABL before operating on ASP OS memory. Access through a compromised ASP user application or ABL is required; successful exploitation compromises firmware-memory integrity and can interrupt secure-processor services.
The record
- CVE
- CVE-2021-46779
- Published
- Jan 10, 2023
- Updated
- Apr 9, 2025
- Vendor
- AMD
- Product
- AMD EPYC 7002 Series Processors
- Classifications
- CWE-787
- 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?
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