Memory integrity loss via stale IOMMU mappings
Published May 11, 2022 · Updated Sep 16, 2024
Improper TLB invalidation in 3rd Gen AMD EPYC processors allows local users to cause an I/O device to write unauthorized memory. The IOMMU fails to flush stale Translation Lookaside Buffer entries, so an I/O device retains mappings to memory it should no longer access. Exploitation requires local low-privileged access and can corrupt protected memory, compromising integrity without reported disclosure or service interruption.
Summary
What happened
Improper TLB invalidation in 3rd Gen AMD EPYC processors allows local users to cause an I/O device to write unauthorized memory. The IOMMU fails to flush stale Translation Lookaside Buffer entries, so an I/O device retains mappings to memory it should no longer access. Exploitation requires local low-privileged access and can corrupt protected memory, compromising integrity without reported disclosure or service interruption.
The record
- CVE
- CVE-2021-26348
- Published
- May 11, 2022
- Updated
- Sep 16, 2024
- Vendor
- AMD
- Product
- AMD EPYC Processors
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 11, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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
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