HIGH Introduced in 5.0
tipc NodeReset UAF
CVE-2026-99246
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
KernelScan AI8.1HIGH
01Description
In the Linux kernel, the following vulnerability has been resolved: tipc: protect node reset trace dump with node lock The tipc_node_reset_links trace event asks tipc_node_dump() to walk the node's link entries. Unlike the other node events that request link data, this event runs without the node lock. This permits bearer teardown to free a link while the trace callback is dumping it: CPU 0 CPU 1 trace_tipc_node_reset_links() tipc_node_dump() l = n->links[0].link tipc_node_write_lock() kfree(l) n->links[0].link = NULL tipc_node_write_unlock() tipc_link_dump(l) tipc_link_dump() then dereferences the stale pointer. KASAN reported: BUG: KASAN: slab-use-after-free in tipc_link_dump Read of size 4 by task poc/115 Call Trace: tipc_link_dump+0x10cb/0x16b0 tipc_node_dump+0x4bb/0x740 trace_event_raw_event_tipc_node_class+0x258/0x360 tipc_node_reset_links+0x14d/0x1a0 tipc_rcv+0x13f5/0x3030 tipc_udp_recv+0x4e3/0x670 Allocated by task 0: tipc_link_create+0x1e1/0x1020 tipc_node_check_dest+0x7d2/0x11a0 tipc_disc_rcv+0xdbf/0x1430 Freed by task 89: kfree+0x131/0x3c0 tipc_node_link_down+0x267/0x4b0 tipc_node_delete_links+0xec/0x160 bearer_disable+0x107/0x260 Take the node write lock around the trace event. This serializes the dump against tipc_node_link_down(delete=true), which frees the link under the same write lock.
02KernelScan AI Analysis
Risk summary
A use-after-free in the TIPC subsystem allows a remote attacker on the same network to corrupt kernel memory by racing a link-reset trace event against bearer teardown. The vulnerability is triggered by sending crafted TIPC/UDP packets that cause a node link reset while a bearer is being disabled, leading to a kernel panic or potential privilege escalation.
Vulnerability analysis
A trace event in the TIPC cluster networking subsystem reads link data without proper locking, while a separate teardown path can free those same links under a lock. This race allows the trace handler to access a link object after it has been freed, resulting in a use-after-free. The fix adds the missing lock around the trace event. An attacker on the same network can trigger the vulnerable code by sending TIPC packets that cause link resets, racing against bearer teardown operations triggered by administrative actions or network changes.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 5.10 | 5.0 | 5.10.273 | c8b72ca0918e |
| 5.15 | 5.0 | 5.15.224 | 6e492cb98ca6 |
| 6.1 | 5.0 | 6.1.191 | 7bb6a35bd6d6 |
| 6.12 | 5.0 | 6.12.115 | a6101d62ccfa |
| 6.18 | 5.0 | 6.18.59 | b8b7d28dc2b7 |
| 6.6 | 5.0 | 6.6.161 | 6abd93d01b0f |
| 7.2 | 5.0 | 7.2.13 | fa8c78c0e49a |
| mainline | 5.0 | 7.3 | dddf197f29ba |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Affected — no CIP fix yet (latest 6.12.114-cip34) |
| cip/6.1 | Affected — no CIP fix yet (latest 6.1.190-cip62) |
| cip/6.1-rt | Affected — no CIP fix yet (latest 6.1.189-cip61-rt32) |
| cip/5.10 | Affected — no CIP fix yet (latest 5.10.272-cip79) |
| cip/5.10-rt | Affected — no CIP fix yet (latest 5.10.272-cip79-rt35) |