CVE-2024-56633 is a Linux kernel vulnerability in the tcp_bpf subsystem's tcp_bpf_sendmsg path. The flaw is caused by incorrect socket memory accounting during BPF sockmap/sockhash message redirection and drop handling. In the __SK_REDIRECT path, memory was pre-unaccounted based on the intended transmit size, derived from msg->sg.size or a smaller apply_bytes value, before the actual number of bytes sent was finalized. If fewer bytes were transmitted than expected, the code attempted to re-charge the difference later; however, when apply_bytes limited the send size and the send operation failed, part of the message memory could remain improperly accounted. A similar issue existed in the __SK_DROP path, where partial freeing based on tosend could leave the remainder of the message unaccounted for. The fix changes the logic to delay uncharging until the final sent byte count is known and to fully free message memory on error paths. The bug manifests as inconsistent sk memory accounting and kernel warnings during socket destruction.
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.
1 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.