CVE-2026-98011

net/sched: hhf: clamp quantum in change and init paths

N/A
Published: September 25, 2026 at 10:23 AM UTC
Updated: October 19, 2026 at 10:17 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 in change and init paths hhf_change() accepts any quantum 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, ...) in hhf_change() matching fq_codel_change(). Clamp hhf_init() to [256, 1<<20] matching the siblings, and remove the old fallback that only set quantum=256 on overflow. Conditions to recreate the bug: CONFIG_NET_SCH_HHF=y. Requires CAP_NET_ADMIN (namespace-local via unshare -Urn suffices). tc qdisc add dev dummy0 root hhf tc qdisc change dev dummy0 root hhf quantum 1 stab data 32768 size_log 15 cell_log 0

Affected

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

Vendor states this is fixed in 0898c6f9fa9ce2632ae88bd0f34a878ccc6335af (fixed)
Vendor states this is fixed in 1113b674307ffddd402524bd1fd9d7d5629b705b (fixed)
Vendor states this is fixed in 2c6dd9fc86d446a03728c43f3b96d9ae29aa058f (fixed)
Vendor states this is fixed in 2e77947bbf6c166e76c038663832d0914418f761 (fixed)
Vendor states this is fixed in 6570f326a6a96bedf3d1d1dab6acc9f8c29104ec (fixed)
Vendor states this is fixed in a328698d046098e6f55b3b1460cac6bab577be58 (fixed)
Vendor states this is fixed in c364ad3ab3c8a6bce469a5cbf02881ab1324c5da (fixed)
Vendor states this is fixed in eb56a495f59baf6cad5ed80e3ffb9078098b1346 (fixed)
Vendor states this is fixed in 3.14 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (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