Loading vulnerability…
CVE-2026-22979 is a Linux kernel networking vulnerability in skb_segment_list() affecting GRO-generated SKB_GSO_FRAGLIST packet handling during packet forwarding. The flaw was introduced after a change in GRO ownership transfer caused fraglist entries to be explicitly orphaned by clearing their socket association, while skb_segment_list() continued to apply legacy truesize accounting logic that subtracted fragment truesize from the parent SKB. Because the fragments no longer carried socket ownership, this subtraction became invalid and caused socket memory to be under-accounted when the head SKB was freed. The result is that sk_wmem_alloc can remain non-zero, preventing socket destruction and causing a persistent kernel memory leak. The fix removes the incorrect truesize adjustment for this code path while preserving skb_release_head_state() so that references to SKB extensions are still correctly released.
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 vulnerability involving a memory leak in networking caused by incorrect GRO packet handling.
A Linux kernel networking vulnerability in skb_segment_list for GRO packets that causes incorrect socket memory accounting, preventing socket destruction and resulting in a persistent memory leak.
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.