Answer in brief
CVE-2026-23074 records a High severity (CVSS 7.8) vulnerability in net/sched: Enforce that teql can only be used as root qdisc. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-23074 records a High severity (CVSS 7.8) vulnerability in net/sched: Enforce that teql can only be used as root qdisc. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <73d970ff0eddd874a84c953387c7f4464b705fc6 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ae810e6a8ac4fe25042e6825d2a401207a2e41fb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dad49a67c2d817bfec98e6e45121b351e3a0202c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0686bedfed34155520f3f735cbf3210cb9044380 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4c7e8aa71c9232cba84c289b4b56cba80b280841 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <16ed73c1282d376b956bff23e5139add061767ba || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3b | 73d970ff0eddd874a84c953387c7f4464b705fc6, ae810e6a8ac4fe25042e6825d2a401207a2e41fb, dad49a67c2d817bfec98e6e45121b351e3a0202c, 0686bedfed34155520f3f735cbf3210cb9044380, 4c7e8aa71c9232cba84c289b4b56cba80b280841, 16ed73c1282d376b956bff23e5139add061767ba, 50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3b |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Feb 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
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 <[email protected]> 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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <73d970ff0eddd874a84c953387c7f4464b705fc6 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ae810e6a8ac4fe25042e6825d2a401207a2e41fb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dad49a67c2d817bfec98e6e45121b351e3a0202c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0686bedfed34155520f3f735cbf3210cb9044380 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4c7e8aa71c9232cba84c289b4b56cba80b280841 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <16ed73c1282d376b956bff23e5139add061767ba || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3b | 73d970ff0eddd874a84c953387c7f4464b705fc6, ae810e6a8ac4fe25042e6825d2a401207a2e41fb, dad49a67c2d817bfec98e6e45121b351e3a0202c, 0686bedfed34155520f3f735cbf3210cb9044380, 4c7e8aa71c9232cba84c289b4b56cba80b280841, 16ed73c1282d376b956bff23e5139add061767ba, 50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3b |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Feb 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
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 <[email protected]> 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.
Quoted source text, attributed separately from HOL analysis.