Loading vulnerability…
CVE-2025-68325 is a queue-accounting vulnerability in the Linux kernel's CAKE queueing discipline (sch_cake). The cake_drop() function uses qdisc_tree_reduce_backlog() to update queue length and backlog throughout the queueing-discipline hierarchy. Its caller, cake_enqueue(), assumes that the parent queueing discipline will enqueue the current packet. When cake_enqueue() returns NET_XMIT_CN, the parent does not enqueue that packet, invalidating the accounting assumption. The resulting inconsistent queue length and backlog can cause a NULL pointer dereference, including when qfq_qdisc is the parent, and lead to a kernel crash or denial of service.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2025-68325, a low-severity NULL pointer dereference vulnerability in the Linux kernel's sch_cake queue discipline (qdisc) when used as a child of qfq. The repository contains two files: a detailed README.md explaining the vulnerability, affected versions, and the kernel patch, and a shell script (tc_poc.sh) that sets up the required qdisc hierarchy on the loopback interface and sends crafted ping packets to trigger the bug. The exploit is local and requires root privileges, as it manipulates kernel network scheduling structures using the 'tc' utility. The main targets are the loopback interface ('lo') and the local IP address (127.0.0.1). Successful exploitation can lead to a kernel crash (denial of service) on vulnerable systems.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.