Memory corruption via partially initialized DRTM UApp
Published May 10, 2022 · Updated Aug 3, 2024
Improper initialization in AMD 3rd Gen EPYC processors allows local users to corrupt memory through crafted SMM inputs. The SMM path mishandles invalid input, leaving the DRTM UApp partially initialized so later mailbox commands perform unchecked memory writes. Low-privileged local access is required, and the bounded consequence is loss of memory integrity.
Summary
What happened
Improper initialization in AMD 3rd Gen EPYC processors allows local users to corrupt memory through crafted SMM inputs. The SMM path mishandles invalid input, leaving the DRTM UApp partially initialized so later mailbox commands perform unchecked memory writes. Low-privileged local access is required, and the bounded consequence is loss of memory integrity.
The record
- CVE
- CVE-2021-26353
- Published
- May 10, 2022
- Updated
- Aug 3, 2024
- Vendor
- Advanced Micro Devices, Inc.
- Product
- 3rd Gen AMD EPYC Processors
- Classifications
- CWE-665
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 10, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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