CVE-2025-68768 is a Linux kernel availability vulnerability in the inet fragmentation/defragmentation path during network namespace teardown. Pending SKBs can remain in fragment queues while still holding conntrack references. Because conntrack depends on nf_defrag_ipv6, nf_defrag_ipv6 may load first and therefore its network-namespace exit hooks run after conntrack's exit hook. In this ordering, conntrack cleanup can loop indefinitely in nf_conntrack_cleanup_net_list() while fragment-queue SKBs still retain references, leading to deadlock conditions involving pernet_ops_rwsem. The upstream fix flushes all fragment queue SKBs in fqdir_pre_exit() so conntrack references are released before conntrack cleanup runs, and also flushes queues from timer expiry handlers when fqdir->dead is set to handle races where packets arrive during pre-exit cleanup.
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.
4 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.