CVE-2026-74609
Received Received - Intake

Use-After-Free in Linux Kernel TIPC Module

Vulnerability report for CVE-2026-74609, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-22

Last updated on: 2026-08-22

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: read le->link under the node lock in tipc_node_link_down() tipc_node_link_down() caches the link pointer before taking n->lock: struct tipc_link *l = le->link; /* unlocked */ if (!l) return; tipc_node_write_lock(n); if (!tipc_link_is_establishing(l)) { /* deref l */ ... tipc_link_reset(l); /* write into l */ if (delete) { kfree(l); le->link = NULL; The delete=true caller frees that very object under n->lock, so the lock does not protect the cached pointer against it: - CPU A, delete=false: tipc_rcv() on TIPC_LINK_DOWN_EVT, or the link supervision timer via tipc_node_timeout(), reads l unlocked and then dereferences it under n->lock; - CPU B, delete=true: netlink TIPC_NL_BEARER_DISABLE -> bearer_disable() -> tipc_node_delete_links() -> tipc_node_link_down(n, bearer_id, true) -> kfree(l). The link is freed with plain kfree(), not kfree_rcu(), and for UDP bearers disable_media() only schedules the asynchronous cleanup_bearer() work, so its synchronize_net() runs after the links are already gone. An in-flight CPU A that has read l therefore dereferences freed memory once B frees it: a use-after-free read in tipc_link_is_establishing(), and a use-after-free write via tipc_link_reset() on the establishing branch. The following trace was captured on 7.2.0-rc5-00284-gaf39eb111ce6: BUG: KASAN: slab-use-after-free in tipc_link_is_establishing (net/tipc/link.c:285) Read of size 4 at addr ffff88802e2aa068 by task swapper/2/0 tipc_link_is_establishing (net/tipc/link.c:285) tipc_node_link_down (net/tipc/node.c:1076) tipc_node_timeout (net/tipc/node.c:843) Allocated by task 9549: tipc_link_create (net/tipc/link.c:490) tipc_node_check_dest (net/tipc/node.c:1279) tipc_disc_rcv (net/tipc/discover.c:252) tipc_udp_recv (net/tipc/udp_media.c:389) Freed by task 9549: tipc_node_link_down (net/tipc/node.c:1084) tipc_node_delete_links (net/tipc/node.c:1320) bearer_disable (net/tipc/bearer.c:414) __tipc_nl_bearer_disable (net/tipc/bearer.c:992) Move the le->link read inside tipc_node_write_lock(), so it is serialised against the kfree() in the delete path. A racing teardown now either has not run yet, and we see a valid link, or has already run, and we see NULL.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-22
Last Modified
2026-08-22
Generated
2026-08-22
AI Q&A
2026-08-22
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux kernel 7.2.0-rc5-00284-gaf39eb111ce6

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a use-after-free vulnerability in the Linux kernel's TIPC (Transparent Inter-Process Communication) module. It occurs when a link pointer is cached without proper locking, allowing a race condition where one CPU reads the pointer while another frees the memory it points to. The issue stems from tipc_node_link_down() reading the link pointer before acquiring the node lock, enabling a concurrent teardown operation to free the link while the cached pointer is still in use.

Detection Guidance

This vulnerability involves a use-after-free in the Linux kernel's TIPC module. Detection requires checking for kernel crashes or KASAN reports related to tipc_link_is_establishing or tipc_node_link_down. Monitor system logs for slab-use-after-free errors in TIPC functions.

Impact Analysis

This vulnerability can lead to system instability, crashes, or potential privilege escalation if exploited. An attacker could trigger a use-after-free condition, causing memory corruption that may result in arbitrary code execution. Systems using TIPC, particularly those with UDP bearers, are at risk of denial-of-service or more severe security breaches if the flaw is exploited.

Mitigation Strategies

Apply the kernel patch that moves the le->link read inside tipc_node_write_lock() to prevent the race condition. If patching is not immediately possible, disable the TIPC module by unloading the tipc kernel module or disabling TIPC support in your kernel configuration.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-74609. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart