Loading vulnerability…
CVE-2023-2163 is an incorrect verifier-pruning vulnerability in the Linux kernel BPF/eBPF implementation. The BPF verifier can incorrectly mark unsafe code paths as safe, allowing malicious BPF programs to bypass intended verifier safety assumptions and perform arbitrary reads and writes in kernel memory.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
28 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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 verifier flaw in which incorrect pruning marks unsafe code paths as safe.
Linux kernel eBPF verifier flaw in which incorrect pruning can mark unsafe paths as safe.
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.