Skip to content
CVE PROGRAM SOURCE RECORD7.8 High

CVE-2025-21702

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

Read JSON ↗CVE.org ↗
Status
Published
Published
Updated
Assigning organization
Linux

Description

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 products

Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.

Linux Linux

Default version status: unaffected

  • 57dbb2d83d100ea601c54fe129bfde0678db5dee to < 78285b53266d6d51fa4ff504a23df03852eba84eaffected
  • 57dbb2d83d100ea601c54fe129bfde0678db5dee to < 7a9723ec27aff5674f1fd4934608937f1d650980affected
  • 57dbb2d83d100ea601c54fe129bfde0678db5dee to < a56a6e8589a9b98d8171611fbcc1e45a15fd2455affected
  • 57dbb2d83d100ea601c54fe129bfde0678db5dee to < 020ecb76812a0526f4130ab5aeb6dc7c773e7ab9affected
  • 57dbb2d83d100ea601c54fe129bfde0678db5dee to < 79a955ea4a2e5ddf4a36328959de0de496419888affected
  • 57dbb2d83d100ea601c54fe129bfde0678db5dee to < e40cb34b7f247fe2e366fd192700d1b4f38196caaffected
  • 57dbb2d83d100ea601c54fe129bfde0678db5dee to < b6a079c3b6f95378f26e2aeda520cb3176f7067baffected
  • 57dbb2d83d100ea601c54fe129bfde0678db5dee to < 647cef20e649c576dff271e018d5d15d998b629daffected

Linux Linux

Default version status: affected

  • 2.6.34affected
  • 0 to < 2.6.34unaffected
  • 5.4.291 to ≤ 5.4.*unaffected
  • 5.10.235 to ≤ 5.10.*unaffected
  • 5.15.179 to ≤ 5.15.*unaffected
  • 6.1.130 to ≤ 6.1.*unaffected
  • 6.6.83 to ≤ 6.6.*unaffected
  • 6.12.14 to ≤ 6.12.*unaffected
  • 6.13.3 to ≤ 6.13.*unaffected
  • 6.14 to ≤ *unaffected

References