CVE-2026-23074

Advisory lineage Upstream: 0 Downstream: 178
Modified
Published: 04 Feb 2026, 16:07
Last modified:11 May 2026, 21:59

Vulnerability Summary

Overall Risk (default)
medium
31/100
CVSS Score
7.8 HIGH
v3.1 (nvd)
EPSS Score
0.02% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

04 Feb 2026, 16:07
Published
Vulnerability first disclosed
11 May 2026, 21:59
Last Modified
Vulnerability information updated

Description

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 Metrics

  • v3.1HIGHScore: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.02% Percentile: 4%

Techniques & Countermeasures

  • CWE-416Use After Free

    The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

  • linuxlinux

    ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 73d970ff0eddd874a84c953387c7f4464b705fc6 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < ae810e6a8ac4fe25042e6825d2a401207a2e41fb | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < dad49a67c2d817bfec98e6e45121b351e3a0202c | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 0686bedfed34155520f3f735cbf3210cb9044380 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4c7e8aa71c9232cba84c289b4b56cba80b280841 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 16ed73c1282d376b956bff23e5139add061767ba | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3b | 2.6.12

  • linuxlinux_kernel

    ≥ 2.6.12.1, < 5.10.249 | ≥ 5.11, < 5.15.199 | ≥ 5.16, < 6.1.162 | ≥ 6.2, < 6.6.122 | ≥ 6.7, < 6.12.68 | ≥ 6.13, < 6.18.8 | 2.6.12 | 2.6.12:rc2 | 2.6.12:rc3 | 2.6.12:rc4 | 2.6.12:rc5 | 6.19:rc1 | 6.19:rc2 | 6.19:rc3 | 6.19:rc4 | 6.19:rc5 | 6.19:rc6

References (7)