CVE-2026-23074In the Linux kernel, the following vulnerability has been resolved: net/sched: Enforce that teql can only be used as root qdisc Design intent of teql is that it is only supposed to be used as root qd…
Updated under an hour ago ()
Does this affect you?
It affects linux_kernel. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: net/sched: Enforce that teql can only be used as root qdisc Design intent of teql is that it is only supposed to be used as root qdisc. We need to check for that constraint. Although not important, I will describe the scenario that unearthed this issue for the curious. GangMin Kim <km.kim1503@gmail.com> managed to concot a scenario as follows: ROOT qdisc 1:0 (QFQ) ├── class 1:1 (weight=15, lmax=16384) netem with delay 6.4s └── class 1:2 (weight=1, lmax=1514) teql GangMin sends a packet which is enqueued to 1:1 (netem). Any invocation of dequeue by QFQ from this class will not return a packet until after 6.4s. In the meantime, a second packet is sent and it lands on 1:2. teql's enqueue will return success and this will activate class 1:2. Main issue is that teql only updates the parent visible qlen (sch->q.qlen) at dequeue. Since QFQ will only call dequeue if peek succeeds (and teql's peek always returns NULL), dequeue will never be called and thus the qlen will remain as 0. With that in mind, when GangMin updates 1:2's lmax value, the qfq_change_class calls qfq_deact_rm_from_agg. Since the child qdisc's qlen was not incremented, qfq fails to deactivate the class, but still frees its pointers from the aggregate. So when the first packet is rescheduled after 6.4 seconds (netem's delay), a dangling pointer is accessed causing GangMin's causing a UAF.
- CVSS
- 7.8 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-416, CWE-825
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Modified
- Record last updated
- Jul 15, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
linux linux_kernel linux:linux_kernel | from 2.6.12.1 before 5.10.249; from 5.11 before 5.15.199; from 5.16 before 6.1.162; from 6.2 before 6.6.122; from 6.7 before 6.12.68; from 6.13 before 6.18.8; 2.6.12; 2.6.12; and 9 more ranges | NVD |
References
- https://git.kernel.org/stable/c/0686bedfed34155520f3f735cbf3210cb9044380patch
- https://git.kernel.org/stable/c/16ed73c1282d376b956bff23e5139add061767bapatch
- https://git.kernel.org/stable/c/4c7e8aa71c9232cba84c289b4b56cba80b280841patch
- https://git.kernel.org/stable/c/50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3bpatch
- https://git.kernel.org/stable/c/73d970ff0eddd874a84c953387c7f4464b705fc6patch
- https://git.kernel.org/stable/c/ae810e6a8ac4fe25042e6825d2a401207a2e41fbpatch
- https://git.kernel.org/stable/c/dad49a67c2d817bfec98e6e45121b351e3a0202cpatch
- https://access.redhat.com/errata/RHSA-2026:3083
- https://access.redhat.com/errata/RHSA-2026:3110
- https://access.redhat.com/errata/RHSA-2026:3268
- https://access.redhat.com/errata/RHSA-2026:3277
- https://access.redhat.com/errata/RHSA-2026:3360
- https://access.redhat.com/errata/RHSA-2026:3388
- https://access.redhat.com/errata/RHSA-2026:3634
- https://access.redhat.com/errata/RHSA-2026:3685
- https://access.redhat.com/errata/RHSA-2026:3810
- https://access.redhat.com/security/cve/CVE-2026-23074
- https://bugzilla.redhat.com/show_bug.cgi?id=2436791
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-23074.json
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.