<?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-10-02T14:10:07.844862+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-74255</id>
    <title>CVE-2026-74255 — tipc: fix UAF in tipc_l2_send_msg()</title>
    <updated>2026-10-02T14:10:07.846944+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 tipc_l2_send_msg()</p>
<p>Syzbot reported a slab-use-after-free in ipvlan_hard_header() when
called from tipc_l2_send_msg().</p>
<p>The root cause is that tipc_disable_l2_media() calls synchronize_net()
while b-&gt;media_ptr is still valid. This allows concurrent RCU readers
to obtain the device pointer after synchronize_net() has finished.
The pointer is cleared later in bearer_disable(), but without any
subsequent synchronization, allowing the device to be freed while
still in use by readers.</p>
<p>Fix this by clearing b-&gt;media_ptr in tipc_disable_l2_media() before
calling synchronize_net().</p>
<p>This is safe to do now because the call order in bearer_disable()
was reversed in 0d051bf93c06 ("tipc: make bearer packet filtering generic")
to call tipc_node_delete_links() (which needs the pointer) before
disable_media().</p>
<p>https: //lore.kernel.org/netdev/6a2c1007.428ffe26.258b27.015d.GAE@google.com/T/#u</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-74255"/>
  </entry>
</feed>
