<?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>Mon, 28 Sep 2026 23:15:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97419 — hsr: broadcast netlink notifications in the device's net namespace</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97419</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;hsr: broadcast netlink notifications in the device&amp;#39;s net namespace&lt;/p&gt;
&lt;p&gt;The HSR generic netlink family sets .netnsok = true. HSR devices can
live in network namespaces other than init_net.&lt;/p&gt;
&lt;p&gt;Two async notifiers broadcast events with genlmsg_multicast(). They
are hsr_nl_ringerror() and hsr_nl_nodedown(). That helper delivers
only on the default genl socket in init_net. So the events always land
in init_net. The network namespace of the device does not matter.&lt;/p&gt;
&lt;p&gt;This has two effects. A listener in the device&amp;#39;s own namespace never
sees its own ring error and node down events. A privileged listener in
init_net receives events from HSR devices in other namespaces. The
payload carries the peer node MAC (HSR_A_NODE_ADDR) and the slave port
ifindex (HSR_A_IFINDEX).&lt;/p&gt;
&lt;p&gt;Switch both callers to genlmsg_multicast_netns(). Other families with
.netnsok = true already do this. Examples are gtp, ovpn, team,
batman-adv, netdev-genl, ethtool and handshake.&lt;/p&gt;
&lt;p&gt;hsr_nl_ringerror() already has the slave port. It uses
dev_net(port-&amp;gt;dev). hsr_nl_nodedown() takes the namespace from the
master port via hsr_port_get_hsr().&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;hsr: broadcast netlink notifications in the device&amp;#39;s net namespace&lt;/p&gt;
&lt;p&gt;The HSR generic netlink family sets .netnsok = true. HSR devices can
live in network namespaces other than init_net.&lt;/p&gt;
&lt;p&gt;Two async notifiers broadcast events with genlmsg_multicast(). They
are hsr_nl_ringerror() and hsr_nl_nodedown(). That helper delivers
only on the default genl socket in init_net. So the events always land
in init_net. The network namespace of the device does not matter.&lt;/p&gt;
&lt;p&gt;This has two effects. A listener in the device&amp;#39;s own namespace never
sees its own ring error and node down events. A privileged listener in
init_net receives events from HSR devices in other namespaces. The
payload carries the peer node MAC (HSR_A_NODE_ADDR) and the slave port
ifindex (HSR_A_IFINDEX).&lt;/p&gt;
&lt;p&gt;Switch both callers to genlmsg_multicast_netns(). Other families with
.netnsok = true already do this. Examples are gtp, ovpn, team,
batman-adv, netdev-genl, ethtool and handshake.&lt;/p&gt;
&lt;p&gt;hsr_nl_ringerror() already has the slave port. It uses
dev_net(port-&amp;gt;dev). hsr_nl_nodedown() takes the namespace from the
master port via hsr_port_get_hsr().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97419</guid>
    </item>
  </channel>
</rss>
