CVE-2024-26669 is a memory leak in the Linux kernel traffic-control flower classifier's chain-template offload lifecycle. When a qdisc is deleted, the traffic-control stack unbinds the driver's flow-offload callback and replays destruction of ordinary filters, but historically did not replay destruction of chain templates. Consequently, an offload-capable driver that allocated resources for a flower chain template did not receive the template-destruction notification and retained those allocations. The fix adds template reoffload handling and emits template create or destroy notifications as flow-offload callbacks are bound or unbound.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel traffic-control flower classifier chain-template offload flaw.
A Linux kernel net/sched flower subsystem vulnerability involving chain-template offload handling. The referenced assessment characterizes its estimated impact as low.
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.