Kernel memory disclosure via poisoned return predictions
Published Jul 12, 2022 · Updated Nov 20, 2024
Speculative execution in affected AMD processors allows local users to read arbitrary kernel memory through poisoned return predictions. On affected microarchitectures, an indirect jump poisons the branch target buffer so a kernel return speculates to an attacker-selected disclosure gadget, exposing cache state. Exploitation requires unprivileged local code execution and a susceptible AMD processor; demonstrated Linux attacks recovered privileged kernel data, including password hashes.
Summary
What happened
Speculative execution in affected AMD processors allows local users to read arbitrary kernel memory through poisoned return predictions. On affected microarchitectures, an indirect jump poisons the branch target buffer so a kernel return speculates to an attacker-selected disclosure gadget, exposing cache state. Exploitation requires unprivileged local code execution and a susceptible AMD processor; demonstrated Linux attacks recovered privileged kernel data, including password hashes.
The record
- CVE
- CVE-2022-29900
- Published
- Jul 12, 2022
- Updated
- Nov 20, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-212, T1003.008
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 12, 2022CVE publishedPublication date reported by the CVE source.
- Nov 20, 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
Public exploit references
- RETBleed Artifactfunctional · demonstrated
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