CVE-2025-21702

published 18 Feb 2025 · updated 11 Nov 2026

pfifo_tail_enqueue: Drop new packet when sch->limit == 0

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.4.291, Kernel 5.15.179, Kernel 6.1.130 and 12 more.

In the Linux kernel, the following vulnerability has been resolved: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return `NET_XMIT_CN` status code. Weird behaviour: In case we set `sch->limit == 0` and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return `NET_XMIT_CN` status code. The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B. - Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let's say Qdisc_A's type is `hfsc`. Enqueue packet to this qdisc will trigger `hfsc_enqueue`. - Qdisc_B's type is pfifo_head_drop. Enqueue packet to this qdisc will trigger `pfifo_tail_enqueue`. - Qdisc_B is configured to have `sch->limit == 0`. - Qdisc_A is configured to route the enqueued's packet to Qdisc_B. Enqueue packet through Qdisc_A will lead to: - hfsc_enqueue(Qdisc_A) -> pfifo_tail_enqueue(Qdisc_B) - Qdisc_B->q.qlen += 1 - pfifo_tail_enqueue() return `NET_XMIT_CN` - hfsc_enqueue() check for `NET_XMIT_SUCCESS` and see `NET_XMIT_CN` => hfsc_enqueue() don't increase qlen of Qdisc_A. The whole process lead to a situation where Qdisc_A->q.qlen == 0 and Qdisc_B->q.qlen == 1. Replace 'hfsc' with other type (for example: 'drr') still lead to the same problem. This violate the design where parent's qlen should equal to the sum of its childrens'qlen. Bug impact: This issue can be used for user->kernel privilege escalation when it is reachable.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=2.6.34 <5.4.291, >=5.11 <5.15.179, >=5.16 <6.1.130, >=5.5 <5.10.235, >=6.13 <6.13.3, >=6.2 <6.6.83, >=6.7 <6.12.14, =6.14, >=57dbb2d83d100ea601c54fe129bfde0678db5dee <647cef20e649c576dff271e018d5d15d998b629d, >=57dbb2d83d100ea601c54fe129bfde0678db5dee <78285b53266d6d51fa4ff504a23df03852eba84e, >=57dbb2d83d100ea601c54fe129bfde0678db5dee <79a955ea4a2e5ddf4a36328959de0de496419888, >=57dbb2d83d100ea601c54fe129bfde0678db5dee <7a9723ec27aff5674f1fd4934608937f1d650980, >=57dbb2d83d100ea601c54fe129bfde0678db5dee <a56a6e8589a9b98d8171611fbcc1e45a15fd2455, >=57dbb2d83d100ea601c54fe129bfde0678db5dee <b6a079c3b6f95378f26e2aeda520cb3176f7067b, >=57dbb2d83d100ea601c54fe129bfde0678db5dee <e40cb34b7f247fe2e366fd192700d1b4f38196ca, =2.6.34, >=57dbb2d83d100ea601c54fe129bfde0678db5dee <020ecb76812a0526f4130ab5aeb6dc7c773e7ab95.4.291, 5.15.179, 6.1.130, 5.10.235, 6.13.3, 6.6.83, 6.12.14, 647cef20e649c576dff271e018d5d15d998b629d, 78285b53266d6d51fa4ff504a23df03852eba84e, 79a955ea4a2e5ddf4a36328959de0de496419888, 7a9723ec27aff5674f1fd4934608937f1d650980, a56a6e8589a9b98d8171611fbcc1e45a15fd2455, b6a079c3b6f95378f26e2aeda520cb3176f7067b, e40cb34b7f247fe2e366fd192700d1b4f38196ca, 020ecb76812a0526f4130ab5aeb6dc7c773e7ab9
linux-kernel: Kernel>=2.6.34 <5.4.291, >=5.11.0 <5.15.179, >=5.16.0 <6.1.130, >=5.5.0 <5.10.235, >=6.13.0 <6.13.3, >=6.2.0 <6.6.83, >=6.7.0 <6.12.145.4.291, 5.15.179, 6.1.130, 5.10.235, 6.13.3, 6.6.83, 6.12.14

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-21702 severity on Zeptric[![CVE-2025-21702](https://zeptric.io/badge/cve/CVE-2025-21702.svg)](https://zeptric.io/cve/CVE-2025-21702)