Privileged-memory disclosure via shared branch history
Published Mar 11, 2022 · Updated May 5, 2025
Branch History Injection in some Intel Processors allows local users to read privileged memory through speculative execution. Shared branch-history state lets unprivileged code steer an indirect predictor to a privileged disclosure gadget, whose transient cache effects reveal data. Exploitation requires local low-privilege code execution and a usable disclosure gadget; the demonstrated Linux exploit reads arbitrary kernel memory.
Summary
What happened
Branch History Injection in some Intel Processors allows local users to read privileged memory through speculative execution. Shared branch-history state lets unprivileged code steer an indirect predictor to a privileged disclosure gadget, whose transient cache effects reveal data. Exploitation requires local low-privilege code execution and a usable disclosure gadget; the demonstrated Linux exploit reads arbitrary kernel memory.
The record
- CVE
- CVE-2022-0001
- Published
- Mar 11, 2022
- Updated
- May 5, 2025
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel Processors
- Classifications
- T1003.008
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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=See references
What conditions does exploitation require?
What is affected?
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
Public exploit references
- VUSec Branch History Injection exploitfunctional · validated
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