Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 51 days later

    Published

  3. · 21 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-21702, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 57dbb2d83d100ea601c54fe129bfde0678db5dee – < 78285b53266d6d51fa4ff504a23df03852eba84e
    • affected 57dbb2d83d100ea601c54fe129bfde0678db5dee – < 7a9723ec27aff5674f1fd4934608937f1d650980
    • affected 57dbb2d83d100ea601c54fe129bfde0678db5dee – < a56a6e8589a9b98d8171611fbcc1e45a15fd2455
    • affected 57dbb2d83d100ea601c54fe129bfde0678db5dee – < 020ecb76812a0526f4130ab5aeb6dc7c773e7ab9
    • affected 57dbb2d83d100ea601c54fe129bfde0678db5dee – < 79a955ea4a2e5ddf4a36328959de0de496419888
    • affected 57dbb2d83d100ea601c54fe129bfde0678db5dee – < e40cb34b7f247fe2e366fd192700d1b4f38196ca
    • affected 57dbb2d83d100ea601c54fe129bfde0678db5dee – < b6a079c3b6f95378f26e2aeda520cb3176f7067b
    • affected 57dbb2d83d100ea601c54fe129bfde0678db5dee – < 647cef20e649c576dff271e018d5d15d998b629d
  • Linux · Linux

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

References

References14

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-21702 badge
[![CVE-2025-21702](https://cveledger.app/badge/CVE-2025-21702.svg)](https://cveledger.app/cve/CVE-2025-21702)

Record last updated .