<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 16:13:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74255 — tipc: fix UAF in tipc_l2_send_msg()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74255</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: fix UAF in tipc_l2_send_msg()&lt;/p&gt;
&lt;p&gt;Syzbot reported a slab-use-after-free in ipvlan_hard_header() when
called from tipc_l2_send_msg().&lt;/p&gt;
&lt;p&gt;The root cause is that tipc_disable_l2_media() calls synchronize_net()
while b-&amp;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.&lt;/p&gt;
&lt;p&gt;Fix this by clearing b-&amp;gt;media_ptr in tipc_disable_l2_media() before
calling synchronize_net().&lt;/p&gt;
&lt;p&gt;This is safe to do now because the call order in bearer_disable()
was reversed in 0d051bf93c06 (&amp;#34;tipc: make bearer packet filtering generic&amp;#34;)
to call tipc_node_delete_links() (which needs the pointer) before
disable_media().&lt;/p&gt;
&lt;p&gt;https: //lore.kernel.org/netdev/6a2c1007.428ffe26.258b27.015d.GAE@google.com/T/#u&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: fix UAF in tipc_l2_send_msg()&lt;/p&gt;
&lt;p&gt;Syzbot reported a slab-use-after-free in ipvlan_hard_header() when
called from tipc_l2_send_msg().&lt;/p&gt;
&lt;p&gt;The root cause is that tipc_disable_l2_media() calls synchronize_net()
while b-&amp;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.&lt;/p&gt;
&lt;p&gt;Fix this by clearing b-&amp;gt;media_ptr in tipc_disable_l2_media() before
calling synchronize_net().&lt;/p&gt;
&lt;p&gt;This is safe to do now because the call order in bearer_disable()
was reversed in 0d051bf93c06 (&amp;#34;tipc: make bearer packet filtering generic&amp;#34;)
to call tipc_node_delete_links() (which needs the pointer) before
disable_media().&lt;/p&gt;
&lt;p&gt;https: //lore.kernel.org/netdev/6a2c1007.428ffe26.258b27.015d.GAE@google.com/T/#u&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74255</guid>
    </item>
  </channel>
</rss>
