CVE-2026-98010 json
net/sched: drr: clamp quantum in change class
published last mo. modified 23d ago also EUVD-2026-86663
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net/sched: drr: clamp quantum in change class
drr_change_class() rejects explicit quantum==0 but falls back to psched_mtu() with no floor. With a crafted size table qdisc_pkt_len reaches ~2 GiB, so quantum=1 (or a zero psched_mtu on a headerless device) makes the deficit-refill loop spin under the qdisc lock.
Add clamp_t(u32, quantum, 256, 1<<20) after the zero reject and on the fallback path. The explicit-zero reject is preserved.
Conditions to recreate the bug: CONFIG_NET_SCH_DRR=y. Requires CAP_NET_ADMIN (namespace-local via unshare -Urn suffices).
tc qdisc add dev dummy0 root drr tc class add dev dummy0 parent 1: classid 1:1 drr quantum 1
Patch / fix
- Linux Linux 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.2.7, 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.7-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-98010
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98010
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.87.3
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.87.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.87.3
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.87.3
- kernel-default SLE Workstation Extension 15 SP7, SLE Module for Legacy 15 SP7, SLE Module for Basesystem 15 SP7 +2 more 6.4.0-150700.53.87.3
suse advisories SUSE-SU-2026:4940-1SUSE-SU-2026:4935-1SUSE-SU-2026:24473-1SUSE-SU-2026:24553-1SUSE-SU-2026:24422-1SUSE-SU-2026:24446-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.40.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.40.1
opensuse advisories openSUSE-SU-2026:22167-1openSUSE-SU-2026:12074-1
- kernel Azure Linux 3.0 6.6.158.1-1
azure linux advisories AZL-104258
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/e2297bbf9cf6ece86f1d1f8c683517a994990f9e commit
- git.kernel.org/stable/c/560794ee6e040b6e1c4ac2b3c8909f341a4596ee commit
- git.kernel.org/stable/c/23fea7e6736b2e1c6f6f2f05cccf33d36834da73 commit
- git.kernel.org/stable/c/b464affe9f9dfe41ac48930c376e3fb8596651b0 commit
- git.kernel.org/stable/c/dc8b374214ef5bba4882bbd95b361e42555cfc0d commit
- git.kernel.org/stable/c/d43cded350fe1218493ad3d37a276aff14108ae6 commit
- git.kernel.org/stable/c/8f756ae1c87414ce9cc21b30e6e4c036d6e9e80b commit
- git.kernel.org/stable/c/8382abec0f1568d0a5590d75a3df92f23fcf5196 commit
Is CVE-2026-98010 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98010 updated cvss 5.5
kernel: net/sched: drr: clamp quantum in change class
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8affected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/e2297bbf9cf6ece86f1d1f8c683517a994990f9e
- git.kernel.org /stable/c/560794ee6e040b6e1c4ac2b3c8909f341a4596ee
- git.kernel.org /stable/c/23fea7e6736b2e1c6f6f2f05cccf33d36834da73
- git.kernel.org /stable/c/b464affe9f9dfe41ac48930c376e3fb8596651b0
- git.kernel.org /stable/c/dc8b374214ef5bba4882bbd95b361e42555cfc0d
- git.kernel.org /stable/c/d43cded350fe1218493ad3d37a276aff14108ae6
- git.kernel.org /stable/c/8f756ae1c87414ce9cc21b30e6e4c036d6e9e80b
- git.kernel.org /stable/c/8382abec0f1568d0a5590d75a3df92f23fcf5196
Sources
- CVE List CVE-2026-98010
- NVD CVE-2026-98010
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.