CVE-2026-43037 is a Linux kernel vulnerability in the ip6_tunnel subsystem, specifically in ip4ip6_err(). The flaw occurs when ip4ip6_err() calls icmp_send() on a cloned skb whose cb[] control buffer was previously populated by the IPv6 receive path as struct inet6_skb_parm. Later, icmp_send() passes IPCB(skb2) to __ip_options_echo(), which interprets the same cb[] region as struct inet_skb_parm for IPv4 processing. Because the IPv6 and IPv4 skb control-buffer layouts differ, inet6_skb_parm.nhoff at offset 14 overlaps inet_skb_parm.opt.rr, which can yield a non-zero rr value. __ip_options_echo() then reads optlen from attacker-controlled packet data at sptr[rr+1] and copies that many bytes into dopt->__data, a fixed 40-byte stack buffer defined by IP_OPTIONS_DATA_FIXED_SIZE. This creates a stack-based buffer overflow condition in kernel context. The upstream fix clears skb2->cb[] before reuse and adds minimal IPv4 header validation requiring version == 4 and ihl >= 5.
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.
16 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.