CVE-2026-72404
Received Received - Intake

Use-After-Free in Linux Kernel TIPC UDP Media Bearer

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

Publication date: 2026-08-15

Last updated on: 2026-08-17

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy() TIPC UDP media bearer teardown calls dst_cache_destroy() on its replicast caches before calling synchronize_net() to wait for concurrent RCU readers (transmitters) to finish: static void cleanup_bearer(struct work_struct *work) { ... list_for_each_entry_safe(rcast, tmp, &ub->rcast.list, list) { dst_cache_destroy(&rcast->dst_cache); list_del_rcu(&rcast->list); kfree_rcu(rcast, rcu); } ... dst_cache_destroy(&ub->rcast.dst_cache); udp_tunnel_sock_release(ub->sk); synchronize_net(); ... } This is highly buggy because dst_cache_destroy() immediately frees the per-CPU cache memory (free_percpu()) and releases the cached dst entries without any synchronization. If a concurrent transmitter (e.g., tipc_udp_xmit()) is running on another CPU under RCU protection, it can call dst_cache_get() concurrently, leading to: 1. Use-After-Free on the per-CPU cache pointer itself (crash). 2. "rcuref - imbalanced put()" warning if it attempts to release a dst that was concurrently released by dst_cache_destroy(). Furthermore, calling kfree(ub) immediately after synchronize_net() without closing the socket first (or waiting after closing it) leaves a window where a concurrent receiver (tipc_udp_recv()) could start after synchronize_net(), access ub, and suffer a UAF when kfree(ub) runs. To fix this, we must defer dst_cache_destroy() and kfree(ub) until after we have ensured that no more readers can see the bearer/socket and all existing readers have finished: 1. Defer rcast entry destruction (both dst_cache_destroy() and kfree()) to an RCU callback using call_rcu_hurry(). Using call_rcu_hurry() ensures the dst entries are released quickly. 2. Release the bearer socket using udp_tunnel_sock_release() (stops new receive readers). 3. Call synchronize_net() to wait for all outstanding RCU readers (both transmit and receive) to finish. 4. Now that it is safe, call dst_cache_destroy() on the main bearer cache, and free ub. Note: 3) and 4) can be changed later in net-next to also use call_rcu_hurry() and get rid of the synchronize_net() latency.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-17
Generated
2026-09-04
AI Q&A
2026-08-15
EPSS Evaluated
2026-09-03
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux_kernel linux_kernel *

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 (UAF) vulnerability in the Linux kernel's TIPC (Transparent Inter-Process Communication) module. It occurs during UDP media bearer teardown when dst_cache_destroy() is called prematurely before synchronize_net() completes. This allows concurrent RCU-protected transmitters to access freed memory, causing crashes or imbalanced reference warnings.

Detection Guidance

This vulnerability is specific to the Linux kernel's TIPC UDP media bearer implementation and requires kernel-level inspection. Detection involves checking kernel logs for crashes related to dst_cache operations or RCU warnings. Commands like dmesg | grep -i 'tipc\|dst_cache\|rcu' may help identify related issues.

Impact Analysis

The vulnerability can cause system crashes due to memory corruption when concurrent processes access freed memory. It may also trigger kernel warnings about imbalanced reference counts. Systems using TIPC over UDP media bearers are particularly affected.

Compliance Impact

This vulnerability is a use-after-free (UAF) issue in the Linux kernel's TIPC UDP media bearer teardown. It does not directly affect compliance with standards like GDPR or HIPAA, as those focus on data protection, privacy, and security controls rather than kernel-level memory management flaws.

Mitigation Strategies

Apply the kernel patch that defers dst_cache_destroy() and kfree() operations until after synchronize_net(). Update to a kernel version containing the fix. If immediate patching is not possible, disable the TIPC module using modprobe -r tipc or blacklist it.

Chat Assistant

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

EPSS Chart