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-90076net/sched: fq: add overflow bounds to quantum and initial quantum

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: fq: add overflow bounds to quantum and initial quantum fq_init() computes quantum = 2 * psched_mtu() and initial_quantum = 10 * psched_mtu() with no overflow check. A device with a huge MTU (e.g. dummy with max_mtu == 0 accepting MTU 2147483634) makes psched_mtu() return 0x80000000; the 2 * and 10 * multiplications wrap to 0 in 32-bit arithmetic, so q->quantum == 0. Then in fq_dequeue() the credit-refill loop adds 0 to f->credit (which stays <= 0) and goto begin loops forever under the qdisc lock, creating a soft lockup. Clamp psched_mtu() to [1, 1 << 20] before multiplying so the product cannot wrap, then cap the result at 1 << 20, matching the bound already enforced on TCA_FQ_QUANTUM in fq_change(). Conditions to recreate the bug: a device whose MTU (plus hard_header_len) is large enough that 2 * psched_mtu() wraps (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. · 43 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.21% · top 88% of all CVEs (16 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 afe4fd062416b158a8a8538b23adc1930a9b88dc – < cf398f67d9caa71af3b9fb9319058b22fe6b524e
    • affected afe4fd062416b158a8a8538b23adc1930a9b88dc – < fd63409b669f9951f1cc6b02486a5254103800d1
    • affected afe4fd062416b158a8a8538b23adc1930a9b88dc – < d16dac3925be95ad46e986d4b139c9898b6e227f
    • affected afe4fd062416b158a8a8538b23adc1930a9b88dc – < f6b3e3848a5fca63438984acd6d9eceac80814c1
    • affected afe4fd062416b158a8a8538b23adc1930a9b88dc – < e35acd56f244d94355f9ab237c2ecc8fba5e6f04
    • affected afe4fd062416b158a8a8538b23adc1930a9b88dc – < 709f34f7c28dc4dd6c40343d101850f11e172312
  • Linux · Linux

    • affected 3.12
    • unaffected < 3.12
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .