Loading vulnerability…
CVE-2024-26591 is a NULL-pointer dereference in the Linux kernel BPF tracing-program attachment path, specifically the re-attachment branch of bpf_tracing_prog_attach. A raw tracepoint program can be used as the target of an fentry program, after which repeatedly creating tracing links without a target file descriptor leaves required attachment metadata unavailable. The vulnerable code subsequently dereferences the absent attachment BTF data, crashing the kernel.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity Linux kernel eBPF tracing attachment flaw that can cause a local kernel crash through a NULL-pointer dereference during re-attachment of a tracing program. Google COS systems using sys-kernel/lakitu-kernel-6_1 before version 18203.0.0 are identified as affected.
Vulnerability addressed by the AlmaLinux 9.2 TuxCare advisory.
A vulnerability included in the TuxCare AlmaLinux 9.2 kernel security update advisory.
Linux kernel BPF tracing-program attachment flaw in bpf_tracing_prog_attach().
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.