CVE-2024-26669 is a memory-leak vulnerability in the Linux kernel traffic-control flower classifier's chain-template hardware-offload lifecycle. When a qdisc is deleted, the traffic-control stack unbinds the driver's flow-block callback and replays destruction of ordinary filters, but historically did not replay destruction of chain templates. Consequently, drivers supporting flower chain-template offload do not receive the FLOW_CLS_TMPLT_DESTROY command and retain allocations associated with the template. The upstream fix adds template reoffload handling and causes flower to emit template create or destroy commands during flow-block bind and unbind processing.
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.
9 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.
Linux kernel net/sched flower classifier chain-template offload issue.
Unknown
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.