CVE-2026-90109

published 17 Sep 2026 · updated 1 Nov 2026

net: sched: fix 32-bit backlog wrap in gred, bfifo and plug enqueue

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3fb51b3960342bbee563543f8d33710fd0fb5a96, Kernel 4c660ee8c809637909f4f7eb1017f7b9401c75c4, Kernel 771a1123570b487765bcf2d4cff3567e66bf1322 and 3 more.

In the Linux kernel, the following vulnerability has been resolved: net: sched: fix 32-bit backlog wrap in gred, bfifo and plug enqueue gred_enqueue(), bfifo_enqueue() and plug_enqueue() admit a packet when the current backlog plus the packet length fits within the queue limit: sch->qstats.backlog + qdisc_pkt_len(skb) <= sch->limit (gred default VQ) gred_backlog+qdisc_pkt_len(skb) <= q->limit (gred configured VQ) sch->qstats.backlog + qdisc_pkt_len(skb) <= sch->limit (bfifo) sch->qstats.backlog + skb->len <= q->limit (plug) sch->qstats.backlog and q->backlog are u32, and qdisc_pkt_len()/skb->len are unsigned int, so all sums are computed in 32 bits and wrap at 2^32. Once the true backlog exceeds 4 GiB the wrapped sum becomes small and admission keeps succeeding, so the queue grows without bound and the kernel can be driven to OOM. Promote the sums to u64 so admission stops once the true backlog exceeds the limit. The limit is u32, so the bounded queue stays below 2^32 and the stored u32 backlog never wraps. The bug can only be reproduced as root (albeit with ridiculous setup): attach a gred (or bfifo/plug) qdisc with a limit near 4 GiB, leaving the default VQ unconfigured (for gred), and drive >4 GiB of queued traffic (e.g. via a size table / stab to inflate qdisc_pkt_len, or sustained high-rate traffic). The u32 backlog+len sum wraps at 2^32, admission keeps succeeding, and the queue grows unboundedly to OOM.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.2, >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <3fb51b3960342bbee563543f8d33710fd0fb5a96, >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <4c660ee8c809637909f4f7eb1017f7b9401c75c4, >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <771a1123570b487765bcf2d4cff3567e66bf1322, >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <8b2d8c70b969bf84f9e248bfaf2a7135129f2eb6, >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <c5ca77024812563fe15c4f7aa906791c3683e9fd, >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <d98b92f3d57976ae185238946ec5ea0be32195aa3fb51b3960342bbee563543f8d33710fd0fb5a96, 4c660ee8c809637909f4f7eb1017f7b9401c75c4, 771a1123570b487765bcf2d4cff3567e66bf1322, 8b2d8c70b969bf84f9e248bfaf2a7135129f2eb6, c5ca77024812563fe15c4f7aa906791c3683e9fd, d98b92f3d57976ae185238946ec5ea0be32195aa

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-90109 severity on Zeptric[![CVE-2026-90109](https://zeptric.io/badge/cve/CVE-2026-90109.svg)](https://zeptric.io/cve/CVE-2026-90109)