CVE-2026-72404

tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy()

CVE-2026-72404 is fixed in 16 products on 1 platform, first by DEBIAN-CVE-2026-72404, released August 15, 2026. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.8
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0016
5th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
dtb-aarch64 · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-64kb · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-64kb · sles 15.7 6.4.0-150700.53.84.1 SUSE-SU-2026:4706-1 Nov 7, 2026
kernel-64kb · sles 16.0 6.12.0-160000.39.1 SUSE-SU-2026:24235-1 Nov 7, 2026
kernel-azure · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-azure · sles 15.7 6.4.0-150700.53.84.1 SUSE-SU-2026:4706-1 Nov 7, 2026
kernel-azure · sles 16.0 6.12.0-160000.39.1 SUSE-SU-2026:24235-1 Nov 7, 2026
kernel-default · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-default · sles 15.7 6.4.0-150700.53.84.1 SUSE-SU-2026:4706-1 Nov 7, 2026
kernel-default · sles 16.0 6.12.0-160000.39.1 SUSE-SU-2026:24197-1 Nov 7, 2026
kernel-default-base · opensuse-leap 16.0 6.12.0-160000.39.1.160000.2.25 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-default-base · sles 15.7 6.4.0-150700.53.84.1.150700.17.47.1 SUSE-SU-2026:4706-1 Nov 7, 2026
kernel-default-base · sles 16.0 6.12.0-160000.39.1.160000.2.26 SUSE-SU-2026:24235-1 Nov 7, 2026
kernel-docs · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-docs · sles 15.7 6.4.0-150700.53.84.1 SUSE-SU-2026:4706-1 Nov 7, 2026
kernel-docs · sles 16.0 6.12.0-160000.39.1 SUSE-SU-2026:24235-1 Nov 7, 2026
kernel-kvmsmall · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-kvmsmall · sles 16.0 6.12.0-160000.39.1 SUSE-SU-2026:24235-1 Nov 7, 2026
kernel-livepatch-SLE15-SP7-RT_Update_21 · sles 15.7 1-150700.1.3.1 SUSE-SU-2026:4640-1 Nov 7, 2026
kernel-livepatch-SLE15-SP7_Update_22 · sles 15.7 1-150700.15.3.1 SUSE-SU-2026:4706-1 Nov 7, 2026
kernel-obs-build · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-obs-build · sles 15.7 6.4.0-150700.53.84.1 SUSE-SU-2026:4706-1 Nov 7, 2026
kernel-obs-qa · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-obs-qa · sles 16.0 6.12.0-160000.39.1 SUSE-SU-2026:24235-1 Nov 7, 2026
kernel-rt · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-source · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-source · sles 15.7 6.4.0-150700.53.84.1 SUSE-SU-2026:4706-1 Nov 7, 2026
kernel-source · sles 16.0 6.12.0-160000.39.1 SUSE-SU-2026:24235-1 Nov 7, 2026
kernel-syms · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-syms · sles 15.7 6.4.0-150700.53.84.1 SUSE-SU-2026:4706-1 Nov 7, 2026
kernel-syms · sles 16.0 6.12.0-160000.39.1 SUSE-SU-2026:24235-1 Nov 7, 2026
kernel-zfcpdump · opensuse-leap 16.0 6.12.0-160000.39.1 OPENSUSE-SU-2026:22091-1 Nov 7, 2026
kernel-zfcpdump · sles 15.7 6.4.0-150700.53.84.1 SUSE-SU-2026:4706-1 Nov 7, 2026
kernel-zfcpdump · sles 16.0 6.12.0-160000.39.1 SUSE-SU-2026:24235-1 Nov 7, 2026
linux · Debian 13.5 (trixie) 6.12.115-2 DEBIAN-CVE-2026-72404 Aug 15, 2026
linux · Debian 14 7.1.5-1 DEBIAN-CVE-2026-72404 Aug 15, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.