Loading vulnerability…
CVE-2024-36883 is a race condition in the Linux kernel networking subsystem's network-namespace generic-data allocation path. net_alloc_generic() reads max_gen_ptrs twice without synchronization: once to size a variable-length allocation and again to initialize the associated bounds length. Concurrent registration of a per-network-namespace operation can increase max_gen_ptrs between those reads, causing the recorded length to exceed the allocated array size. Subsequent initialization in ops_init can therefore access the array out of bounds. The upstream fix snapshots max_gen_ptrs once in net_alloc_generic(); later growth is handled by net_assign_generic().
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.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel networking vulnerability involving out-of-bounds access in ops_init.
Linux kernel networking out-of-bounds access flaw in ops_init.
A Linux kernel networking flaw involving an out-of-bounds access in ops_init.
Linux kernel networking flaw involving an out-of-bounds access in ops_init.
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.