Kernel memory corruption via stack-map allocation overflow
Published Oct 1, 2021 · Updated Aug 4, 2024
Out-of-bounds write in Linux kernel before 5.14.12 allows local users to crash the system via a crafted eBPF stack map. In prealloc_elems_and_freelist, a 32-bit elem_size wraps during multiplication by max_entries, so bpf_map_area_alloc reserves too little memory before pcpu_freelist_populate writes beyond the allocation. Reachability requires local ability to create the affected eBPF map; the confirmed result is kernel memory corruption that can terminate the system.
Summary
What happened
Out-of-bounds write in Linux kernel before 5.14.12 allows local users to crash the system via a crafted eBPF stack map. In prealloc_elems_and_freelist, a 32-bit elem_size wraps during multiplication by max_entries, so bpf_map_area_alloc reserves too little memory before pcpu_freelist_populate writes beyond the allocation. Reachability requires local ability to create the affected eBPF map; the confirmed result is kernel memory corruption that can terminate the system.
The record
- CVE
- CVE-2021-41864
- Published
- Oct 1, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 2021CVE 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.
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.
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