Bug 2436791 (CVE-2026-23074) - CVE-2026-23074 kernel: Linux kernel: Use-after-free in teql queueing discipline can lead to privilege escalation
Summary: CVE-2026-23074 kernel: Linux kernel: Use-after-free in teql queueing discipli...
Keywords:
Status: NEW
Alias: CVE-2026-23074
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-04 17:03 UTC by OSIDB Bzimport
Modified: 2026-03-05 03:17 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:3083 0 None None None 2026-02-23 13:12:19 UTC
Red Hat Product Errata RHSA-2026:3110 0 None None None 2026-02-23 18:06:32 UTC
Red Hat Product Errata RHSA-2026:3268 0 None None None 2026-02-25 00:18:03 UTC
Red Hat Product Errata RHSA-2026:3277 0 None None None 2026-02-25 04:03:44 UTC
Red Hat Product Errata RHSA-2026:3360 0 None None None 2026-02-25 15:16:52 UTC
Red Hat Product Errata RHSA-2026:3388 0 None None None 2026-02-26 04:22:55 UTC
Red Hat Product Errata RHSA-2026:3634 0 None None None 2026-03-03 09:51:30 UTC
Red Hat Product Errata RHSA-2026:3685 0 None None None 2026-03-03 20:34:28 UTC
Red Hat Product Errata RHSA-2026:3810 0 None None None 2026-03-05 03:17:19 UTC

Description OSIDB Bzimport 2026-02-04 17:03:34 UTC
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> 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.

Comment 3 errata-xmlrpc 2026-02-23 13:12:18 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:3083 https://access.redhat.com/errata/RHSA-2026:3083

Comment 4 errata-xmlrpc 2026-02-23 18:06:31 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:3110 https://access.redhat.com/errata/RHSA-2026:3110

Comment 5 errata-xmlrpc 2026-02-25 00:18:02 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.6 Telecommunications Update Service

Via RHSA-2026:3268 https://access.redhat.com/errata/RHSA-2026:3268

Comment 6 errata-xmlrpc 2026-02-25 04:03:43 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2026:3277 https://access.redhat.com/errata/RHSA-2026:3277

Comment 7 errata-xmlrpc 2026-02-25 15:16:51 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On

Via RHSA-2026:3360 https://access.redhat.com/errata/RHSA-2026:3360

Comment 8 errata-xmlrpc 2026-02-26 04:22:54 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.2 Advanced Update Support

Via RHSA-2026:3388 https://access.redhat.com/errata/RHSA-2026:3388

Comment 9 errata-xmlrpc 2026-03-03 09:51:29 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2026:3634 https://access.redhat.com/errata/RHSA-2026:3634

Comment 10 errata-xmlrpc 2026-03-03 20:34:26 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2026:3685 https://access.redhat.com/errata/RHSA-2026:3685

Comment 11 errata-xmlrpc 2026-03-05 03:17:18 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Extended Lifecycle Support  - EXTENSION

Via RHSA-2026:3810 https://access.redhat.com/errata/RHSA-2026:3810


Note You need to log in before you can comment on or make changes to this bug.