CVE-2026-98012

net/sched: sfq: clamp quantum in change path

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: sfq: clamp quantum in change path sfq_change() accepts any non-negative quantum (only rejects (int)ctl->quantum < 0). 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, ...) matching fq_codel_change(). Reject quantum > 1<<20 with -EINVAL, matching fq_codel_change() and the init clamp. Conditions to recreate the bug: CONFIG_NET_SCH_SFQ=y. Requires CAP_NET_ADMIN (namespace-local via unshare -Urn suffices). tc qdisc add dev dummy0 root sfq tc qdisc change dev dummy0 root sfq 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.

4919649699c5f4dbae08b8e2ed536fc9d6c3c2aa5.10.2395.15.1865.4.297548cf048b426729a7a1fa6acd1271c010c9a738058ae7465f0e7113d45aa88a66bf2d203c71c195e6.1.1296.12.136.136.6.7682bd38bd5467ece1ee274b493f51326cf5220a5a843cacb88f42f426973f1ed11c6fb562558efb27c49ac48fac51a6a54efd5963954d02bacf075085e4650d7ae4252f67e997a632adfae0dd74d3a99a
Vendor states this is fixed in 0692ce5a528df450d64e9f819054177e9d91076f (fixed)
Vendor states this is fixed in 4117c528b2de5fdc3e4a7e3626815b616a635cdc (fixed)
Vendor states this is fixed in 534cd7ecbbc6e8a974f4003a5c1557439c6e0a72 (fixed)
Vendor states this is fixed in e4192bcf83aaab02129644ddf4656fd86e93751f (fixed)
Vendor states this is fixed in e6c1cb728e389354203a72bc77464c222a247aeb (fixed)
Vendor states this is fixed in f3820dce042a673fcb28cc31c87ee14257e21a17 (fixed)
Vendor states this is fixed in f82fa6f10d4a69322cad0f7a4aa523ce6292a5a0 (fixed)
Vendor states this is fixed in fb9f88a33c516ea5c0bcd9a22ca288b246b34567 (fixed)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
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.13 (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