CVE-2026-90075

net/sched: fq_codel: clamp default quantum and mtu

N/A
Published: September 17, 2026 at 04:05 PM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: fq_codel: clamp default quantum and mtu fq_codel_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_codel_dequeue(), causing an infinite loop and soft lockup. Emulate fq_codel_change() and constrain to [256, FQ_CODEL_QUANTUM_MAX]. The same unclamped psched_mtu() is assigned to q->cparams.mtu a bit below, and fq_codel_change() never updates it. codel_should_drop() tests "*backlog <= params->mtu"; with mtu == 0x80000000 (~2 GiB) and the default 32 MiB memory_limit, the test is always true, so CoDel is silently and completely disabled (no drops, no ECN). Declare a single clamped mtu and assign both q->quantum and q->cparams.mtu from it, which also removes the double psched_mtu() call. 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.54b549a2ef4bef9965d97cbd992ba67930cd3e0fe
Vendor states this is fixed in 324f86806673ae4a55f66d28db84577f46f615e1 (fixed)
Vendor states this is fixed in 3782067ec0d485628b6f1f9ede3eeeb4f611fcf2 (fixed)
Vendor states this is fixed in 397e2b1f71d9f15b8b4e47d24eb620e4dff8878d (fixed)
Vendor states this is fixed in 9f499e5827fdb6d7fdb46a7ce731852f6b1a1bb9 (fixed)
Vendor states this is fixed in a9a5b2943a00df2ab81a2209f31dd9e87016f120 (fixed)
Vendor states this is fixed in d315ee8a07fd1810880227319cf60e6cd925ef22 (fixed)
Vendor states this is fixed in d9ebd8f9aa8b2773235889cb903fafd61f2d8585 (fixed)
Vendor states this is fixed in dfb4b61db886917244284b18b44b23d2254b82c2 (fixed)
Vendor states this is fixed in 3.5 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card