CVE-2026-72390net/sched: sch_teql: Introduce slaves_lock to avoid race condition and UAF
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_teql: Introduce slaves_lock to avoid race condition and UAF The teql master->slaves singly linked list is not protected against multiple writes. It can be mod'ed concurently from teql_master_xmit(), teql_dequeue(), teql_init() and teql_destroy() without holding any list lock or RCU protection. [email protected] has demonstrated that the qdisc is freed after an RCU grace period, but teql_master_xmit() running on another CPU can still hold a stale pointer into the list, resulting in a slab-use-after-free: BUG: KASAN: slab-use-after-free in teql_master_xmit+0xf0f/0x16b0 Read of size 8 at addr ffff888013fb0440 by task poc/332 Freed 512-byte region [ffff888013fb0400, ffff888013fb0600) (kmalloc-512) The fix? Add a per-master slaves_lock spinlock that serializes all mutations of master->slaves and the NEXT_SLAVE() links in teql_destroy() and teql_qdisc_init(). teql_master_xmit() also takes the same slaves_lock around those updates. Annotate master->slaves and the per-slave ->next pointer with __rcu and use the appropriate RCU accessors everywhere they are touched: rcu_assign_pointer() on the writer side (under slaves_lock), rcu_dereference_protected() for the writer-side loads (also under slaves_lock), rcu_dereference_bh() for the loads in teql_master_xmit() and rtnl_dereference() for the loads in teql_master_open()/teql_master_mtu(), which run under RTNL. Pair this with rcu_read_lock_bh()/rcu_read_unlock_bh() around the list traversal in teql_master_xmit(), so that readers either observe a fully linked list or are deferred until the in-flight mutation completes. The two early-return paths in teql_master_xmit() are updated to release the RCU-bh read-side critical section before returning, since leaving it held would disable BH on that CPU for good.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 03c67781254c574ae7fa75e881239a78473bdf42
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 735567bde7401f82b064f9f107b52ee1bf84ed8c
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 11402e6e18e96df615cbcc58157818dd604b23ff
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9b7d05cbaa60108642402100efa6aa288dd33023
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b26aa9d993537a4c3167d8ceead3b7c69c3a0aac
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e5b811fe793166aecc59b085c1b7c31262ef2316
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/03c67781254c574ae7fa75e881239a78473bdf42 (opens in a new tab)
- https://git.kernel.org/stable/c/735567bde7401f82b064f9f107b52ee1bf84ed8c (opens in a new tab)
- https://git.kernel.org/stable/c/11402e6e18e96df615cbcc58157818dd604b23ff (opens in a new tab)
- https://git.kernel.org/stable/c/9b7d05cbaa60108642402100efa6aa288dd33023 (opens in a new tab)
- https://git.kernel.org/stable/c/b26aa9d993537a4c3167d8ceead3b7c69c3a0aac (opens in a new tab)
- https://git.kernel.org/stable/c/e5b811fe793166aecc59b085c1b7c31262ef2316 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59289 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72390)Record last updated .