Local memory corruption via insufficient address validation
Published May 9, 2023 · Updated Jan 28, 2025
Insufficient address validation in 3rd Gen AMD EPYC Processors before MilanPI 1.0.0.9 allows local users to corrupt sensitive memory. The AGESA flaw fails to validate an address supplied through a compromised ABL and UApp before accessing protected memory. Control of both firmware components is required, and successful corruption can damage integrity or interrupt platform availability.
Summary
What happened
Insufficient address validation in 3rd Gen AMD EPYC Processors before MilanPI 1.0.0.9 allows local users to corrupt sensitive memory. The AGESA flaw fails to validate an address supplied through a compromised ABL and UApp before accessing protected memory. Control of both firmware components is required, and successful corruption can damage integrity or interrupt platform availability.
The record
- CVE
- CVE-2021-26397
- Published
- May 9, 2023
- Updated
- Jan 28, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- 3rd Gen AMD EPYC Processors
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
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
No sourced classifications are available.
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