Protected-data disclosure via shared branch history
Published May 31, 2023 · Updated Jan 9, 2025
Branch History Injection in Linux Kernel 6.1-rc1 allows local users to infer protected data through shared CPU branch history. The processor reuses Branch History Buffer state across software contexts, letting malicious code steer victim branches into speculative execution that leaves measurable cache allocations. Exploitation requires local code execution on affected AmpereOne hardware and exposes data across software contexts without modifying it.
Summary
What happened
Branch History Injection in Linux Kernel 6.1-rc1 allows local users to infer protected data through shared CPU branch history. The processor reuses Branch History Buffer state across software contexts, letting malicious code steer victim branches into speculative execution that leaves measurable cache allocations. Exploitation requires local code execution on affected AmpereOne hardware and exposes data across software contexts without modifying it.
The record
- CVE
- CVE-2023-3006
- Published
- May 31, 2023
- Updated
- Jan 9, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-212, CWE-226, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 31, 2023CVE publishedPublication date reported by the CVE source.
- Jan 9, 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=Linux Kernel 6.1-rc1
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
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