CVE-2025-21702 is an incorrect queue-length accounting vulnerability in the Linux kernel traffic-control subsystem. In pfifo_tail_enqueue(), a pfifo_head_drop qdisc configured with a zero packet limit can accept a packet when its queue is empty, increment the child qdisc queue length, and return NET_XMIT_CN even though no existing packet was dropped. A parent qdisc, including HFSC or DRR, can treat that result as non-success and not increment its own queue length. This produces an inconsistent hierarchy in which a parent qdisc's qlen does not equal the aggregate qlen of its children.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel packet scheduler limit-handling flaw.
A resolved Linux kernel network traffic-control qdisc accounting flaw in pfifo_tail_enqueue() when sch->limit equals zero. The condition can desynchronize parent and child qdisc queue-length accounting and, when reachable, may enable local user-to-kernel privilege escalation.
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.