CVE-2026-46319 is a use-after-free race in the Linux kernel net/sched act_ct code path, specifically in tcf_ct_flow_table_get() during flow table lookup and reference acquisition. The vulnerable logic calls rhashtable_lookup_fast() to retrieve a tcf_ct_flow_table (ct_ft) from zones_ht. Although the lookup occurs under an internal RCU read-side critical section, that section is exited before refcount_inc_not_zero(&ct_ft->ref) is attempted. This creates a race window in which another path can drop the last reference, remove the object from the hash table, schedule tcf_ct_flow_table_cleanup_work(), and ultimately free ct_ft via kfree(). If cleanup completes between the lookup return and the refcount increment, the caller dereferences and attempts to reference an already freed ct_ft object, resulting in a kernel use-after-free. The upstream fix is to keep the RCU read lock held until the ct_ft reference is safely acquired.
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.
3 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.