Kernel-address disclosure via stale mov32 bounds
Published Feb 11, 2022 · Updated Aug 4, 2024
Improper bounds tracking in the Linux kernel through 5.16-rc5 allows local users to disclose kernel pointer addresses via eBPF mov32 operations. The check_alu_op() verifier path leaves incorrect bounds after a 32-bit register move, allowing pointer-derived arithmetic to become an unknown scalar and be exported through a BPF map. Loading crafted BPF bytecode with low local privileges is sufficient; the demonstrated consequence is address disclosure, not data modification or service interruption.
Summary
What happened
Improper bounds tracking in the Linux kernel through 5.16-rc5 allows local users to disclose kernel pointer addresses via eBPF mov32 operations. The check_alu_op() verifier path leaves incorrect bounds after a 32-bit register move, allowing pointer-derived arithmetic to become an unknown scalar and be exported through a BPF map. Loading crafted BPF bytecode with low local privileges is sufficient; the demonstrated consequence is address disclosure, not data modification or service interruption.
The record
- CVE
- CVE-2021-45402
- Published
- Feb 11, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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
- bpf, selftests: Add test case trying to taint map value pointerproof of concept · 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