GHSA-WVGV-43W8-M5VV
Vulnerability from github – Published: 2026-09-24 18:31 – Updated: 2026-09-24 18:31In the Linux kernel, the following vulnerability has been resolved:
ipv6: use RCU iterator to dump route exceptions
rt6_nh_dump_exceptions() uses hlist_for_each_entry() to iterate over RCU-protected exception lists. The caller holds rcu_read_lock(), but does not hold rt6_exception_lock, so rt6_insert_exception() can concurrently add an entry with hlist_add_head_rcu().
KCSAN reports this race (irrelevant details omitted):
================================================================== BUG: KCSAN: data-race in rt6_insert_exception / rt6_nh_dump_exceptions
write (marked) to 0xffff8a7c44c59620 of 8 bytes by interrupt on cpu 5: rt6_insert_exception+0x3bb/0x760 __ip6_rt_update_pmtu+0x4fe/0x750 ip6_sk_update_pmtu+0x19a/0x3b0 udpv6_err+0x3ff/0x800 icmpv6_notify+0x1e1/0x440 icmpv6_rcv+0x8c0/0xab0 ip6_protocol_deliver_rcu+0x616/0x840 ip6_input_finish+0xb9/0x160 ... entry_SYSCALL_64_after_hwframe+0x77/0x7f
read to 0xffff8a7c44c59620 of 8 bytes by task 549 on cpu 14: rt6_nh_dump_exceptions+0xb3/0x260 rt6_dump_route+0x53e/0x5f0 fib6_dump_node+0x6d/0xf0 fib6_walk_continue+0x290/0x2d0 fib6_dump_table+0x28d/0x360 inet6_dump_fib+0x37d/0x620 rtnl_dumpit+0x7b/0xd0 netlink_dump+0x3ae/0x7e0 ... entry_SYSCALL_64_after_hwframe+0x77/0x7f
4 locks held by dumper/549: ... #1: (rcu_read_lock){....}-{1:3}, at: inet6_dump_fib+0x88/0x620 #2: (&tb->tb6_lock){+.-.}-{3:3}, at: fib6_dump_table+0x1e9/0x360 #3: (rcu_read_lock){....}-{1:3}, at: rt6_dump_route+0x483/0x5f0
value changed: 0xffff8a7c44e05700 -> 0xffff8a7c45d60100
Reported by Kernel Concurrency Sanitizer on: CPU: 14 UID: 0 PID: 549 Comm: dumper Not tainted 7.2.0-rc7-virtme #38 PREEMPT(lazy) ...
Use hlist_for_each_entry_rcu() to safely iterate over the exception list.
{
"affected": [],
"aliases": [
"CVE-2026-93226"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-24T16:17:17Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: use RCU iterator to dump route exceptions\n\nrt6_nh_dump_exceptions() uses hlist_for_each_entry() to iterate over\nRCU-protected exception lists. The caller holds rcu_read_lock(), but does\nnot hold rt6_exception_lock, so rt6_insert_exception() can concurrently\nadd an entry with hlist_add_head_rcu().\n\nKCSAN reports this race (irrelevant details omitted):\n\n ==================================================================\n BUG: KCSAN: data-race in rt6_insert_exception / rt6_nh_dump_exceptions\n\n write (marked) to 0xffff8a7c44c59620 of 8 bytes by interrupt on cpu 5:\n rt6_insert_exception+0x3bb/0x760\n __ip6_rt_update_pmtu+0x4fe/0x750\n ip6_sk_update_pmtu+0x19a/0x3b0\n udpv6_err+0x3ff/0x800\n icmpv6_notify+0x1e1/0x440\n icmpv6_rcv+0x8c0/0xab0\n ip6_protocol_deliver_rcu+0x616/0x840\n ip6_input_finish+0xb9/0x160\n ...\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\n read to 0xffff8a7c44c59620 of 8 bytes by task 549 on cpu 14:\n rt6_nh_dump_exceptions+0xb3/0x260\n rt6_dump_route+0x53e/0x5f0\n fib6_dump_node+0x6d/0xf0\n fib6_walk_continue+0x290/0x2d0\n fib6_dump_table+0x28d/0x360\n inet6_dump_fib+0x37d/0x620\n rtnl_dumpit+0x7b/0xd0\n netlink_dump+0x3ae/0x7e0\n ...\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\n 4 locks held by dumper/549:\n ...\n #1: (rcu_read_lock){....}-{1:3}, at: inet6_dump_fib+0x88/0x620\n #2: (\u0026tb-\u003etb6_lock){+.-.}-{3:3}, at: fib6_dump_table+0x1e9/0x360\n #3: (rcu_read_lock){....}-{1:3}, at: rt6_dump_route+0x483/0x5f0\n\n value changed: 0xffff8a7c44e05700 -\u003e 0xffff8a7c45d60100\n\n Reported by Kernel Concurrency Sanitizer on:\n CPU: 14 UID: 0 PID: 549 Comm: dumper Not tainted\n 7.2.0-rc7-virtme #38 PREEMPT(lazy)\n ...\n\nUse hlist_for_each_entry_rcu() to safely iterate over the exception list.",
"id": "GHSA-wvgv-43w8-m5vv",
"modified": "2026-09-24T18:31:23Z",
"published": "2026-09-24T18:31:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93226"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3665abc3d2ae8a78cb67f858e848481432ec75db"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/47cdab0d51aaa9bd85f8e4904585bd5bd4df4488"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6bd3f94ed858f2d072627546b4cdf712b0f8ea88"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9c6be625e1a7258e845d6193b3b6b084a00f8e9e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a602cd128d17a793e12888edc8eda85821ede7e1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dffbfb3117138e8e0e09d05f507bd36ca1f696e5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/eda56ee17713f9dd834b922f7dbfa2e25fa6358c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f6b1b15848fd91fe122dac0d19d3d666e35075b6"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.