Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0686bedfed34155520f3f735cbf3210cb9044380, 16ed73c1282d376b956bff23e5139add061767ba, 4c7e8aa71c9232cba84c289b4b56cba80b280841.

Low priority for now. Upgrade to Linux Linux 0686bedfed34155520f3f735cbf3210cb9044380, 16ed73c1282d376b956bff23e5139add061767ba, 4c7e8aa71c9232cba84c289b4b56cba80b280841 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Feb 4, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23074

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.12.1 and later · before 5.10.249
  • linux linux kernel5.11 and later · before 5.15.199
  • linux linux kernel5.16 and later · before 6.1.162
  • linux linux kernel6.2 and later · before 6.6.122
  • linux linux kernel6.7 and later · before 6.12.68
  • linux linux kernel6.13 and later · before 6.18.8
  • linux linux kernel2.6.12
  • linux linux kernel6.19

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 73d970ff0eddd874a84c953387c7f4464b705fc6affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ae810e6a8ac4fe25042e6825d2a401207a2e41fbaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before dad49a67c2d817bfec98e6e45121b351e3a0202caffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0686bedfed34155520f3f735cbf3210cb9044380affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 4c7e8aa71c9232cba84c289b4b56cba80b280841affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 16ed73c1282d376b956bff23e5139add061767baaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3baffected · git
    • before 2.6.12not affected · semver
    • 5.10.249 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-23071Feb 4, 2026 · regmap: Fix race condition in hwspinlock irqsave routine
    18Monitor
  • ← EarlierCVE-2026-23073Feb 4, 2026 · wifi: rsi: Fix memory corruption due to not set vif driver data size
    31Monitor
  • Later →CVE-2026-23076Feb 4, 2026 · ALSA: ctxfi: Fix potential OOB access in audio mixer handling
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0686bedfed34155520f3f735cbf3210cb9044380Vendor (CNA)
Linux Linux16ed73c1282d376b956bff23e5139add061767baVendor (CNA)
Linux Linux4c7e8aa71c9232cba84c289b4b56cba80b280841Vendor (CNA)
Linux Linux50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3bVendor (CNA)
Linux Linux73d970ff0eddd874a84c953387c7f4464b705fc6Vendor (CNA)
Linux Linuxae810e6a8ac4fe25042e6825d2a401207a2e41fbVendor (CNA)
Linux Linuxdad49a67c2d817bfec98e6e45121b351e3a0202cVendor (CNA)
almalinux:bpftool4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.92.1.150600.12.42.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-docs6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-kvmsmall6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-build6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-qa6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)

+34

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records