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-90074net/sched: fq_pie: clamp default quantum to avoid signed overflow

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: fq_pie: clamp default quantum to avoid signed overflow fq_pie_init() sets q->quantum = psched_mtu(qdisc_dev(sch)) without clamping. A device with a huge MTU (e.g. dummy with max_mtu == 0 accepting MTU 2147483634) makes psched_mtu() return 0x80000000, which overflows the signed flow->deficit to INT_MIN in fq_pie_qdisc_dequeue(), causing an infinite loop and soft lockup. Emulate fq_pie_policy which is already bounded to [1, 1 << 20]; clamp the default to [256, 1 << 20]. 256 matches fq_codel's floor and is a sane minimum for a DRR quantum. Conditions to recreate the bug: a device whose MTU (plus hard_header_len) wraps psched_mtu() into the sign bit (e.g. a dummy device with max_mtu == 0 accepting MTU 2147483634). Requires CAP_NET_ADMIN in a user namespace.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 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.22% · top 88% 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: Not scored.

Affected products

  • Linux · Linux

    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < 1f43e4dbc93b7d02761a024d5f895df823c07b72
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < f7942b2693bc24c7d609a03d06f97bee3b0bd96a
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < 6f1be05faecef4c0f9a008200209f66ef2e133f7
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < 435da3734a8e63d3067016accc977ed1d10aaaa0
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < 44dad8fe99b58a7fe2961e9eec6a5f07ace5b51f
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < 044fa2498bbc2900f0c48a6ef2fdd5b2bdfc3795
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < bf97fd2163ad1191ef8daa3d4df8372aee19e396
    • affected ec97ecf1ebe485a17cd8395a5f35e6b80b57665a – < c86cd7ed0b0e44779a3d1683f03e4353baf4bdc9
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 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-90074 badge
[![CVE-2026-90074](https://cveledger.app/badge/CVE-2026-90074.svg)](https://cveledger.app/cve/CVE-2026-90074)

Record last updated .