Kernel-address disclosure via atomic-fetch pointer mishandling
Published Feb 4, 2022 · Updated Aug 2, 2024
Information disclosure in the Linux kernel before 5.16-rc6 allows local users to expose kernel pointer addresses through crafted eBPF code. The eBPF verifier fails to preserve pointer-type information for some atomic fetch operations and can return an internal kernel address to userspace. Exploitation requires local access and permission to load eBPF code; the disclosure reveals kernel pointer addresses that weaken exploit mitigations.
Summary
What happened
Information disclosure in the Linux kernel before 5.16-rc6 allows local users to expose kernel pointer addresses through crafted eBPF code. The eBPF verifier fails to preserve pointer-type information for some atomic fetch operations and can return an internal kernel address to userspace. Exploitation requires local access and permission to load eBPF code; the disclosure reveals kernel pointer addresses that weaken exploit mitigations.
The record
- CVE
- CVE-2022-0264
- Published
- Feb 4, 2022
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-755
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 4, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=kernel v5.16-rc6
What conditions does exploitation require?
What is affected?
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