Loading vulnerability…
CVE-2025-38502 is an out-of-bounds memory access vulnerability in Linux kernel BPF cgroup local storage handling. It occurs when a BPF program tail-calls another program that uses cgroup local storage with a different value size. Although the verifier validates each program individually, the runtime bpf_cg_run_ctx retains the originally attached program's bpf_prog_array_item. Consequently, bpf_get_local_storage() in the tail-called program retrieves the original program's storage map instead of its own. Accesses based on the second program's expected storage size can exceed the actual allocation, potentially causing information disclosure, kernel memory corruption, or a kernel crash.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This four-file repository contains a standalone C local privilege-escalation exploit for CVE-2025-38502, a Linux kernel eBPF cgroup-local-storage out-of-bounds vulnerability reachable through eBPF tail calls. The main source, CVE-2025-3850-Linux-LPE-Abaraxas-Labs.c, creates BPF maps and CGROUP_SKB programs, uses a small cgroup-storage map in a caller program and a larger storage map in a tail-called program, then leverages the verifier/runtime map-size mismatch for out-of-bounds access. It sprays BPF array maps, obtains a kernel offset through a userspace-visible data map, overwrites/hijacks BPF map operations, and installs a kernel ROP path intended to elevate credentials and return to spawn /bin/sh. ebpf_lpe.h supplies the exploit context, raw eBPF instruction-building macros, an auxiliary verifier/runtime bounds mismatch primitive, and kernel-structure layout constants. README.md documents the root cause, affected versions, fixes, preconditions, mitigations, and references; .gitignore is nonfunctional. The repository makes no network requests and targets only the local kernel through the bpf syscall. The source filename says CVE-2025-3850, but the README explicitly identifies the published CVE as CVE-2025-38502.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.