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-98013net/sched: fq_pie: clamp quantum in change path

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: fq_pie: clamp quantum in change path fq_pie_change() accepts any quantum value 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, ...) matching fq_codel_change(). Conditions to recreate the bug: CONFIG_NET_SCH_FQ_PIE=y. Requires CAP_NET_ADMIN (namespace-local via unshare -Urn suffices). tc qdisc add dev dummy0 root fq_pie tc qdisc change dev dummy0 root fq_pie 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 (15 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 ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < ff4f3a0f3abd2ded467931d7da7984a68a768e0b
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < 749aaebc1eb92ce2f38fd3caf68a2f99686d84ef
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < 8fd98e56c41f79278eeb67512c28d7abc175bcf4
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < 215df1e953ae72a09d425ec188e054058ae23dc9
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < f90fe65b977e7aa9eb302230a09eb18f8c32ceaa
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < c11e3a39807eb5a200445ae9082843ab86800415
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < 6655b56e2801008566c594ef231f6c7b3f716c61
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < 4864f58c53eb47257d55e01f47d4a9f355f7f970
  • 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-98013 badge
[![CVE-2026-98013](https://cveledger.app/badge/CVE-2026-98013.svg)](https://cveledger.app/cve/CVE-2026-98013)

Record last updated .