high · CVSS 8.1

CVE-2026-99246

tipc: protect node reset trace dump with node lock

Published 3 Nov 2026 · Source updated 3 Nov 2026 · Retrieved 2026-11-04 20:14 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
Software	Version information	Fixed version
LinuxLinux	affected: eb18a510b5cd4daeb9736ad8db57a9fc49db185b to < c8b72ca0918e95f708f67c8b3e69b05290f2b6d2; affected: eb18a510b5cd4daeb9736ad8db57a9fc49db185b to < 6e492cb98ca69cc1145175e23e22e3b84da7f26d; affected: eb18a510b5cd4daeb9736ad8db57a9fc49db185b to < 7bb6a35bd6d69019539d8782fb590fd2aa8a3236; affected: eb18a510b5cd4daeb9736ad8db57a9fc49db185b to < 6abd93d01b0f495f29201925a5ee8e6a583c4044; affected: eb18a510b5cd4daeb9736ad8db57a9fc49db185b to < a6101d62ccfa153db8c218ce59362b8e0316fd4f; affected: eb18a510b5cd4daeb9736ad8db57a9fc49db185b to < b8b7d28dc2b7472ffd1eff3954c38f1976b21a7b; affected: eb18a510b5cd4daeb9736ad8db57a9fc49db185b to < fa8c78c0e49aa11fae116fd841e41aa8f2d68751; affected: eb18a510b5cd4daeb9736ad8db57a9fc49db185b to < dddf197f29ba5e47a476dde82bf542ca2e0d5e5e	See vendor advisory
LinuxLinux	affected: 5.0; unaffected: 0 to < 5.0; unaffected: 5.10.273 to ≤ 5.10.; unaffected: 5.15.224 to ≤ 5.15.; unaffected: 6.1.191 to ≤ 6.1.; unaffected: 6.6.161 to ≤ 6.6.; unaffected: 6.12.115 to ≤ 6.12.; unaffected: 6.18.59 to ≤ 6.18.; unaffected: 7.2.13 to ≤ 7.2.; unaffected: 7.3 to ≤	See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed