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-98009net/sched: ets: clamp quantum in parse and fallback paths

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: ets: clamp quantum in parse and fallback paths ets_qdisc_change() falls back to psched_mtu() with no floor for bands without an explicit quantum. With a crafted size table qdisc_pkt_len reaches ~2 GiB, so a zero psched_mtu on a headerless device makes the deficit-refill loop spin under the qdisc lock. Move the floor into ets_quantum_parse() so explicitly configured quanta are also clamped to [256, 1<<20], not just the fallback path. Conditions to recreate the bug: CONFIG_NET_SCH_ETS=y. Requires CAP_NET_ADMIN (namespace-local via unshare -Urn suffices). tc qdisc add dev dummy0 root ets bands 3 strict 2 quanta 1 1

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 – < 440b66cc7b56ea38e9b878ae88da91992efaa4c4
    • affected dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 – < 4ef8664eafafc8db68a1d52601f17dc008a223b7
    • affected dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 – < 8b8d782c3b96376217087767dcf662cd3d25f226
    • affected dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 – < 226d2702e74a570f5bfae6115b4706da4b94e5cf
    • affected dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 – < 99ae477b892e203a37985ebc56f0063e072f7f4b
    • affected dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 – < 8f80b113dea0bed3c1a31a4224b72775cd9ec52d
    • affected dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 – < de22c30ec5598aca8797f02082d2ee1358dfa3ff
    • affected dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 – < 1c38487f46b243bfeefec0c0c86023a3904f2214
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .