Protected-memory disclosure via branch-predictor aliasing
Published Jul 14, 2022 · Updated Sep 16, 2024
Branch type confusion in affected AMD processors allows local users to infer protected memory through branch-predictor aliasing. The branch predictor treats aliasing instructions as the wrong branch type and speculatively executes at an incorrect target before the pipeline is flushed. Exploitation requires local code execution and can expose kernel data to user space or hypervisor data to a guest, while address-space isolation limits cross-process and cross-VM leakage.
Summary
What happened
Branch type confusion in affected AMD processors allows local users to infer protected memory through branch-predictor aliasing. The branch predictor treats aliasing instructions as the wrong branch type and speculatively executes at an incorrect target before the pipeline is flushed. Exploitation requires local code execution and can expose kernel data to user space or hypervisor data to a guest, while address-space isolation limits cross-process and cross-VM leakage.
The record
- CVE
- CVE-2022-23825
- Published
- Jul 14, 2022
- Updated
- Sep 16, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 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?
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.
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