<?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>Wed, 30 Sep 2026 04:38:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64123 — net: hsr: defer node table free until after RCU readers</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64123</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;net: hsr: defer node table free until after RCU readers&lt;/p&gt;
&lt;p&gt;HSR node-list and node-status generic-netlink operations run under
rcu_read_lock(). They walk hsr-&amp;gt;node_db through hsr_get_next_node() and
hsr_get_node_data(), but RTM_DELLINK teardown removes the same node table
with plain list_del() and frees each node immediately.&lt;/p&gt;
&lt;p&gt;That lets a generic-netlink reader hold a struct hsr_node pointer across
hsr_dellink(). In a KASAN build, widening the reader window after
hsr_get_next_node() obtains the node reproduces a slab-use-after-free
when the reader copies node-&amp;gt;macaddress_A; the freeing stack is
hsr_del_nodes() from hsr_dellink().&lt;/p&gt;
&lt;p&gt;Use list_del_rcu() and defer the free through the existing
hsr_free_node_rcu() callback. This matches the lifetime rule used by the
HSR prune paths, which already delete nodes with list_del_rcu() and
call_rcu().&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;net: hsr: defer node table free until after RCU readers&lt;/p&gt;
&lt;p&gt;HSR node-list and node-status generic-netlink operations run under
rcu_read_lock(). They walk hsr-&amp;gt;node_db through hsr_get_next_node() and
hsr_get_node_data(), but RTM_DELLINK teardown removes the same node table
with plain list_del() and frees each node immediately.&lt;/p&gt;
&lt;p&gt;That lets a generic-netlink reader hold a struct hsr_node pointer across
hsr_dellink(). In a KASAN build, widening the reader window after
hsr_get_next_node() obtains the node reproduces a slab-use-after-free
when the reader copies node-&amp;gt;macaddress_A; the freeing stack is
hsr_del_nodes() from hsr_dellink().&lt;/p&gt;
&lt;p&gt;Use list_del_rcu() and defer the free through the existing
hsr_free_node_rcu() callback. This matches the lifetime rule used by the
HSR prune paths, which already delete nodes with list_del_rcu() and
call_rcu().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64123</guid>
    </item>
  </channel>
</rss>
