GHSA-6RV6-HXHF-8GW6
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33In 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.
zdi-disclosures@trendmicro.com 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.
{
"affected": [],
"aliases": [
"CVE-2026-72390"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:12Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_teql: Introduce slaves_lock to avoid race condition and UAF\n\nThe teql master-\u003eslaves singly linked list is not protected against\nmultiple writes. It can be mod\u0027ed concurently from teql_master_xmit(),\nteql_dequeue(), teql_init() and teql_destroy() without holding any list\nlock or RCU protection.\n\nzdi-disclosures@trendmicro.com has demonstrated that the qdisc is freed\nafter an RCU grace period, but teql_master_xmit() running on another\nCPU can still hold a stale pointer into the list, resulting in a\nslab-use-after-free:\n\nBUG: KASAN: slab-use-after-free in teql_master_xmit+0xf0f/0x16b0\nRead of size 8 at addr ffff888013fb0440 by task poc/332\nFreed 512-byte region [ffff888013fb0400, ffff888013fb0600) (kmalloc-512)\n\nThe fix?\nAdd a per-master slaves_lock spinlock that serializes all mutations of\nmaster-\u003eslaves and the NEXT_SLAVE() links in teql_destroy() and\nteql_qdisc_init(). teql_master_xmit() also takes the same slaves_lock\naround those updates.\nAnnotate master-\u003eslaves and the per-slave -\u003enext pointer with __rcu and\nuse the appropriate RCU accessors everywhere they are touched:\nrcu_assign_pointer() on the writer side (under slaves_lock),\nrcu_dereference_protected() for the writer-side loads (also under\nslaves_lock), rcu_dereference_bh() for the loads in teql_master_xmit() and\nrtnl_dereference() for the loads in teql_master_open()/teql_master_mtu(),\nwhich run under RTNL.\nPair this with rcu_read_lock_bh()/rcu_read_unlock_bh() around the list\ntraversal in teql_master_xmit(), so that readers either observe a fully\nlinked list or are deferred until the in-flight mutation completes. The two\nearly-return paths in teql_master_xmit() are updated to release the RCU-bh\nread-side critical section before returning, since leaving it held would\ndisable BH on that CPU for good.",
"id": "GHSA-6rv6-hxhf-8gw6",
"modified": "2026-08-17T06:33:27Z",
"published": "2026-08-15T06:32:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72390"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/03c67781254c574ae7fa75e881239a78473bdf42"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/11402e6e18e96df615cbcc58157818dd604b23ff"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/735567bde7401f82b064f9f107b52ee1bf84ed8c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9b7d05cbaa60108642402100efa6aa288dd33023"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b26aa9d993537a4c3167d8ceead3b7c69c3a0aac"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e5b811fe793166aecc59b085c1b7c31262ef2316"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.