CVE-2026-90058net/sched: bound qdisc_pkt_len to prevent qdisc soft lockup
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: net/sched: bound qdisc_pkt_len to prevent qdisc soft lockup qdisc_get_stab() accepts a user-supplied size table, and __qdisc_calculate_pkt_len() amplifies qdisc_pkt_len() through the overhead, the size-table data (u16), and size_log (up to STAB_SIZE_LOG_MAX). A crafted stab can therefore set qdisc_pkt_len() to ~1 GiB for an ordinary skb. Per-flow deficit schedulers such as DRR and ETS replenish one quantum per loop iteration; with a tiny quantum (1) they spin billions of times under the qdisc lock, producing a soft lockup / RCU stall as illustrated by [email protected]. Cap the final qdisc_pkt_len() to QDISC_PKT_LEN_MAX so the size-table amplification cannot drive deficit schedulers into an unbounded loop. A legitimate size table (e.g. qfq's overhead 999999999, which is handled by dropping) is still accepted. Introduce cap QDISC_PKT_LEN_MAX (1 << 20) = 1 MiB which is well above any legitimate single-skb wire length: the largest current skb->len is GSO_MAX_SIZE (524280), and an ATM-style size table (53/48 cell tax) amplifies that to ~578 KB, both comfortably below 1 MiB. At the same time, 1 MiB bounds the deficit refill loop to ~1M iterations per packet with quantum=1, which completes in a few milliseconds well under the demonstrated softlockup threshold (~10^9 iterations). Conditions to recreate the bug: - CONFIG_NET_SCHED=y, CONFIG_NET_SCH_DRR=y (or CONFIG_NET_SCH_ETS=y). - Attach a DRR (or ETS) root qdisc with a crafted TCA_STAB that amplifies qdisc_pkt_len to ~1 GiB (e.g. size_log=15, data=[32768]). - Add a class with a tiny quantum of 1 and send one small packet; the deficit loop spins billions of times under the qdisc lock and trips the softlockup detector (panic with kernel.softlockup_panic=1). - Reachable as root or from an unprivileged user in a fresh user+net namespace (unshare -Urn) with namespace-local CAP_NET_ADMIN.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 32 days later
· 32 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4f0f4b09a95ef602fbdae948326beadd9c20eab3
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0bc5a6280a132a2170c6fa742436e01b635f02de
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 448c34421b38ec7c93a0060a885218ca319d382b
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 82fdbf49b9f7528c82bf608cfa9710e5f81a198c
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6e78792d8ce1fa3561713860ee8086901dde4f99
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1a5c26e586481bc82abc19ac92c3d9f10518f525
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 16d21a27df3f50b7251c9388fc5a7ab22703b469
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8f735d64382dcf162f4276d6699d03ad2f859c0b
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.270 – ≤ 5.10.*
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/4f0f4b09a95ef602fbdae948326beadd9c20eab3 (opens in a new tab)
- https://git.kernel.org/stable/c/0bc5a6280a132a2170c6fa742436e01b635f02de (opens in a new tab)
- https://git.kernel.org/stable/c/448c34421b38ec7c93a0060a885218ca319d382b (opens in a new tab)
- https://git.kernel.org/stable/c/82fdbf49b9f7528c82bf608cfa9710e5f81a198c (opens in a new tab)
- https://git.kernel.org/stable/c/6e78792d8ce1fa3561713860ee8086901dde4f99 (opens in a new tab)
- https://git.kernel.org/stable/c/1a5c26e586481bc82abc19ac92c3d9f10518f525 (opens in a new tab)
- https://git.kernel.org/stable/c/16d21a27df3f50b7251c9388fc5a7ab22703b469 (opens in a new tab)
- https://git.kernel.org/stable/c/8f735d64382dcf162f4276d6699d03ad2f859c0b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81919 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90058)Record last updated .