CVE-2024-33621 is a Linux kernel ipvlan networking flaw in ipvlan_process_v4_outbound() and ipvlan_process_v6_outbound(). The outbound paths reused skb->sk when invoking IPv4 or IPv6 local output. For packets originating from an AF_PACKET socket, skb->sk refers to the packet socket rather than an IP-family socket. In the IPv6 multicast output path, this reaches sk_mc_loop(), which expects an appropriate IP socket family and triggers a WARN_ON_ONCE condition. The fix passes a NULL socket pointer to ip_local_out() and ip6_local_out(), consistent with other tunnel implementations, preventing the packet socket from being interpreted as an IP socket.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel IPvlan networking flaw caused by using skb->sk in IPv4 and IPv6 outbound processing.
Linux kernel IPvlan outbound packet socket-pointer handling flaw.
Linux kernel IPvlan flaw caused by use of skb->sk in IPv4 and IPv6 outbound processing.
Linux kernel ipvlan networking flaw involving use of skb->sk during IPv4 and IPv6 outbound processing.
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.