Look up another CVE · open CVE-2026-72404 in the interactive tracker
CVE-2026-72404
tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy()
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem net/tipc. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-72404 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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 lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
net/tipc/udp_media.c
- What this is
- TIPC NETWORK LAYERMAINTAINERS section matched on net/tipc/ · netdev@vger.kernel.org · Maintained
- Kernel module
- tipc
Check it on the machine
grep -wE 'CONFIG_TIPC|CONFIG_TIPC_MEDIA_UDP' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w tipcPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this as a loadable module. Every release below compiles it as a module on every flavour, so whether the code is in the running kernel depends on whether that module is loaded.
- bookworm, trixie, forky, sidm
- m
- a loadable module on every flavour - check lsmod, can be blacklisted
- Build switches
- CONFIG_TIPC, CONFIG_TIPC_MEDIA_UDP
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-15 (2 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.16%, higher than 4.9% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- net/tipc
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.3 | 6.18.57 | 3827ff67f9fb |
| 5.3 | 7.1.5 | 1c8393eefa3c |
| 5.3 | 7.2 | 7116764ca53f |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The UAF is in cleanup_bearer() during UDP bearer teardown, reached only via TIPC genetlink bearer disable (TIPC_NL_BEARER_DISABLE) or network-namespace exit; remote UDP/TIPC peers cannot initiate teardown, so exploitation requires local netlink/netns access even though concurrent xmit/recv may involve network I/O.
- AC:LAttack complexity, low
- An attacker with namespace CAP_NET_ADMIN can script both teardown and concurrent traffic (enable/disable bearer or destroy netns while sending/receiving TIPC UDP on port 6118), controlling both sides of the RCU race; dst_cache_destroy()'s free_percpu() widens the window and syzbot triggered it reliably.
- PR:LPrivileges required, low
- Bearer disable/enable and netns teardown require CAP_NET_ADMIN; TIPC genetlink ops use GENL_UNS_ADMIN_PERM and tipc_genl_family.netnsok=true, so unprivileged users obtain effective net-admin capability via user/network namespaces (unshare -Urn).
- UI:NUser interaction, none
- Exploitation needs no victim interaction beyond the attacker's own namespace/netlink operations and packet generation; no mount, file open, or other user-directed action is required.
- S:UScope, unchanged
- The use-after-free corrupts kernel heap memory within the same kernel security domain; impacts are kernel crash or local privilege escalation, not VM escape or cross-security-authority boundary crossing.
- C:HConfidentiality impact, high
- Premature dst_cache_destroy() frees per-CPU cache memory while concurrent tipc_udp_xmit() may call dst_cache_get() on the freed object, and the post-synchronize_net() recv path dereferences freed udp_bearer, enabling kernel memory disclosure.
- I:HIntegrity impact, high
- UAF on dst_cache structures and udp_bearer allows heap shaping and control of freed-object contents, providing primitives for arbitrary kernel writes and potential control-flow hijacking/local privilege escalation.
- A:HAvailability impact, high
- Concurrent use-after-free reliably causes kernel oops/panic (per commit: UAF on per-CPU cache pointer crashes) and can be triggered repeatedly during scripted bearer teardown loops.