<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T19:16:08.559439+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-72404</id>
    <title>CVE-2026-72404 — tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy()</title>
    <updated>2026-09-29T19:16:09.320422+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy()</p>
<p>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:</p>
<p>static void cleanup_bearer(struct work_struct *work)
{
...
	list_for_each_entry_safe(rcast, tmp, &amp;ub-&gt;rcast.list, list) {
		dst_cache_destroy(&amp;rcast-&gt;dst_cache);
		list_del_rcu(&amp;rcast-&gt;list);
		kfree_rcu(rcast, rcu);
	}
...
	dst_cache_destroy(&amp;ub-&gt;rcast.dst_cache);
	udp_tunnel_sock_release(ub-&gt;sk);
	synchronize_net();
...
}</p>
<p>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.</p>
<p>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().</p>
<p>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.</p>
<p>To fix this, we must defer dst_cache_destroy() and kfre…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-72404"/>
  </entry>
</feed>
