Loading vulnerability…
CVE-2026-64192 is a Linux kernel vulnerability in BPF inode storage handling. When the kernel is built with CONFIG_BPF_LSM enabled, support for BPF_MAP_TYPE_INODE_STORAGE is compiled in. If the BPF Linux Security Module is not actually initialized at boot time, such as when it is omitted from the active LSM configuration, the initialization path that prepares the BPF LSM security blob layout is never executed. As a result, the inode security blob offset used by BPF remains at an invalid default compiled value rather than a valid runtime offset.
A privileged user that creates and updates an inode storage BPF map can then cause the kernel to access the wrong location within the inode security blob. The erroneous offset aliases the RCU callback structure embedded at the beginning of the security blob. During later cleanup or inode destruction, clearing the owner storage field overwrites the queued RCU callback pointer with NULL. When the kernel later processes that callback, it attempts to execute a NULL function pointer, causing an immediate kernel panic. The fix introduces an initialization flag for the BPF LSM and rejects inode storage map allocation when the supporting BPF LSM infrastructure is not initialized.
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.
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.