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-98011net/sched: hhf: clamp quantum in change and init paths

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: hhf: clamp quantum in change and init paths hhf_change() accepts any quantum from userspace, including 1. With a crafted size table qdisc_pkt_len reaches ~2 GiB, so quantum=1 makes the deficit-refill loop spin ~2^31 times under the qdisc lock (a soft lockup / denial of service). Add max(256U, ...) in hhf_change() matching fq_codel_change(). Clamp hhf_init() to [256, 1<<20] matching the siblings, and remove the old fallback that only set quantum=256 on overflow. Conditions to recreate the bug: CONFIG_NET_SCH_HHF=y. Requires CAP_NET_ADMIN (namespace-local via unshare -Urn suffices). tc qdisc add dev dummy0 root hhf tc qdisc change dev dummy0 root hhf quantum 1 stab data 32768 size_log 15 cell_log 0

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 (18 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 10239edf86f137ce4c39b62ea9575e8053c549a0 – < a328698d046098e6f55b3b1460cac6bab577be58
    • affected 10239edf86f137ce4c39b62ea9575e8053c549a0 – < c364ad3ab3c8a6bce469a5cbf02881ab1324c5da
    • affected 10239edf86f137ce4c39b62ea9575e8053c549a0 – < 2c6dd9fc86d446a03728c43f3b96d9ae29aa058f
    • affected 10239edf86f137ce4c39b62ea9575e8053c549a0 – < 6570f326a6a96bedf3d1d1dab6acc9f8c29104ec
    • affected 10239edf86f137ce4c39b62ea9575e8053c549a0 – < 1113b674307ffddd402524bd1fd9d7d5629b705b
    • affected 10239edf86f137ce4c39b62ea9575e8053c549a0 – < 2e77947bbf6c166e76c038663832d0914418f761
    • affected 10239edf86f137ce4c39b62ea9575e8053c549a0 – < 0898c6f9fa9ce2632ae88bd0f34a878ccc6335af
    • affected 10239edf86f137ce4c39b62ea9575e8053c549a0 – < eb56a495f59baf6cad5ed80e3ffb9078098b1346
  • Linux · Linux

    • affected 3.14
    • unaffected < 3.14
    • 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-98011 badge
[![CVE-2026-98011](https://cveledger.app/badge/CVE-2026-98011.svg)](https://cveledger.app/cve/CVE-2026-98011)

Record last updated .