Local memory disclosure via insufficient LFENCE/JMP serialization
Published Mar 11, 2022 · Updated Sep 17, 2024
Speculative-execution exposure in AMD processors allows local users to infer host memory through a flawed LFENCE/JMP mitigation. The V2-2 LFENCE/JMP sequence leaves a speculative-execution window large enough for branch-target injection despite the intended fence. A local low-privileged context and an affected CPU using this mitigation are required; successful exploitation discloses host memory, including data assigned to other guests.
Summary
What happened
Speculative-execution exposure in AMD processors allows local users to infer host memory through a flawed LFENCE/JMP mitigation. The V2-2 LFENCE/JMP sequence leaves a speculative-execution window large enough for branch-target injection despite the intended fence. A local low-privileged context and an affected CPU using this mitigation are required; successful exploitation discloses host memory, including data assigned to other guests.
The record
- CVE
- CVE-2021-26401
- Published
- Mar 11, 2022
- Updated
- Sep 17, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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