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-2026-52984net/sched: netem: fix queue limit check to include reordered packets

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: netem: fix queue limit check to include reordered packets The queue limit check in netem_enqueue() uses q->t_len which only counts packets in the internal tfifo. Packets placed in sch->q by the reorder path (__qdisc_enqueue_head) are not counted, allowing the total queue occupancy to exceed sch->limit under reordering. Include sch->q.qlen in the limit check.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 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-2026-52984, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 216509dda290f6db92c816dd54b83c1df9da9e76 – < 0f875d52db4c921da610e481b72f03cc82fdcb72
    • affected c2047b0e216c8edce227d7c42f99ac2877dad0e4 – < ef9a41b3870fb90577da5b2de5bd140022d4021e
    • affected 10df49cfca73dfbbdb6c4150d859f7e8926ae427 – < 74fcd8e127200a50ee22ba2b45c164722bdb9177
    • affected 3824c5fad18eeb7abe0c4fc966f29959552dca3e – < 39a66e83ea41fe845631eeb8d326953de27d13f9
    • affected 356078a5c55ec8d2061fcc009fb8599f5b0527f9 – < 54b5dbacd00dedffd5e2eed76de1c3839996b5e6
    • affected f8d4bc455047cf3903cd6f85f49978987dbb3027 – < 8450462eaf91d5d2a9e863507b16d18e814baef3
    • affected f8d4bc455047cf3903cd6f85f49978987dbb3027 – < 936a7dd87251f6f3e88983350833edf60fe6a80b
    • affected f8d4bc455047cf3903cd6f85f49978987dbb3027 – < 4185701fcce6b426b6c3630b25330dddd9c47b0d
    • affected 83c6ab12f08dcc09d4c5ac86fdb89736b28f1d31
    • affected 5.10.232 – < 5.10.258
    • affected 5.15.175 – < 5.15.209
    • affected 6.1.121 – < 6.1.175
    • affected 6.6.67 – < 6.6.141
    • affected 6.12.6 – < 6.12.91
    • affected 5.4.288 – < 5.5
  • Linux · Linux

    • affected 6.13
    • unaffected < 6.13
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.141 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .