CVE-2026-90073

net/sched: hhf: clamp quantum before hhf_change() to avoid overflow

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: hhf: clamp quantum before hhf_change() to avoid overflow hhf_init() sets q->quantum = psched_mtu(qdisc_dev(sch)) with no overflow check. A device with a huge MTU (e.g. dummy with max_mtu == 0 accepting MTU 2147483634) makes weight * quantum overflow the signed deficit in hhf_dequeue(), spinning forever. Clamp q->quantum before hhf_change() so both the opt and !opt paths see a sane quantum. Without this, bare "tc qdisc add ... hhf" succeeds with a clamped quantum but "tc qdisc add ... hhf limit 1000" (any option present) fails with -EINVAL because hhf_change() re-validates the unclamped default (sch_hhf.c:559). 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.

Affected

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

Vendor states this is fixed in 0c66223e90ddb4fd3700965a9241f2fde7bd6bc7 (fixed)
Vendor states this is fixed in 20b65bf7ca06e48ec1d62ed8012f71205328dbe4 (fixed)
Vendor states this is fixed in 2164b512b97bb053e8ce4d6e95576f11bed6a005 (fixed)
Vendor states this is fixed in 2446644b0f6d045b01db6acbaf55552dbec8a59a (fixed)
Vendor states this is fixed in 2e0f0729f922c8de13801004e2131b57646c7c5f (fixed)
Vendor states this is fixed in 99770b5d8e0e1c69b996f74a19d71afd2c4a9aa4 (fixed)
Vendor states this is fixed in dea2789a9d5ff38bdd77f2e64d550430899e2839 (fixed)
Vendor states this is fixed in fa9c2055f0a60f801ccf286af53d387dc6202c3f (fixed)
Vendor states this is fixed in 3.14 (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