cve.bz

CVE-2026-98011 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.271
  • Linux Linux: fixed in 5.15.222
  • Linux Linux: fixed in 6.1.189
  • Linux Linux: fixed in 6.6.158
  • Linux Linux: fixed in 6.12.111
  • Linux Linux: fixed in 6.18.53
  • Linux Linux: fixed in 7.2.7
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-98011 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98011?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98011?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-98011 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux3.14 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.271
Linux5.155.15.222
Linux6.16.1.189
Linux6.66.6.158
Linux6.126.12.111
Linux6.186.18.53
Linux7.27.2.7
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.190-1DEBIAN-CVE-2026-98011
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-98011
Debian13linux6.12.111-1DEBIAN-CVE-2026-98011
Debian14linux7.2.7-1DEBIAN-CVE-2026-98011
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-98011
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-98011
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-98011
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-98011 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-98011 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-98011 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-98011 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-98011 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-98011 USN-8962-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-98011 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-98011 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-98011 USN-9024-1
82 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.9-1.1openSUSE-SU-2026:12074-1
Azure Linux3kernel6.6.158.1-1AZL-104574
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-98011
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-98011
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-98011

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low severity denial of service vulnerability was found in the Linux kernel's Heavy-Hitter Filter (HHF) queueing discipline (net/sched/sch_hhf.c). The hhf_change() function accepts an arbitrarily small quantum value from userspace: when the HHF qdisc is configured with quantum=1 together with a crafted packet size table (for example via the tc command), the deficit-refill loop iterates roughly 2^31 times while holding the qdisc lock, causing a kernel soft lockup and a local denial of service. Triggering the flaw requires CAP_NET_ADMIN privileges, which an unprivileged local user can obtain inside an unprivileged user namespace on kernels built with CONFIG_NET_SCH_HHF; only system availability is affected, with no impact on confidentiality or integrity. In Red Hat's products the vulnerable code is present in Red Hat Enterprise Linux 8 (kernel and kernel-rt) and in the RHEL 8 based OpenShift Container Platform 4.12 CoreOS image, where the fix has been deferred to a future update because the flaw is rated low severity and exploitation requires (namespace-local) CAP_NET_ADMIN privileges for a denial-of-service-only impact; the residual risk is a soft lockup or temporary system hang on affected hosts where untrusted local users are able to create user namespaces. Red Hat Enterprise Linux 6, 7, 9, and 10, Red Hat In-Vehicle OS, and OpenShift Container Platform releases based on RHEL CoreOS 9 are not affected because the vulnerable code is not present in those releases. Although the CVSS:3.1 base score is 5.5 (Moderate), Red Hat rates the impact of this flaw as low because successful exploitation requires CAP_NET_ADMIN (even if obtainable within an unprivileged user namespace) and the result is limited to a local denial of service.

Red Hat's mitigation

The flaw can only be triggered by a user holding CAP_NET_ADMIN. On affected systems, exposure to attacks from unprivileged local users can be reduced by preventing the creation of unprivileged user namespaces, which is the path by which such users can acquire CAP_NET_ADMIN. This can be done by setting the sysctl user.max_user_namespaces to 0, for example with 'sysctl -w user.max_user_namespaces=0' (persisted via a file in /etc/sysctl.d/). Restricting CAP_NET_ADMIN to trusted administrators likewise prevents unprivileged exploitation. Note that disabling unprivileged user namespaces may affect workloads that rely on them, such as unprivileged containers.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-98011.

References

Check your stackJSON