CVE-2026-97419

hsr: broadcast netlink notifications in the device's net namespace

N/A
Published: September 24, 2026 at 04:03 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: hsr: broadcast netlink notifications in the device's net namespace The HSR generic netlink family sets .netnsok = true. HSR devices can live in network namespaces other than init_net. 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. This has two effects. A listener in the device'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). 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. hsr_nl_ringerror() already has the slave port. It uses dev_net(port->dev). hsr_nl_nodedown() takes the namespace from the master port via hsr_port_get_hsr().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.13 ≤ v < 5.10.2713.13 ≤ v < 5.15.2223.13 ≤ v < 6.1.1893.13 ≤ v < 6.12.1113.13 ≤ v < 6.18.533.13 ≤ v < 6.6.1583.13 ≤ v < 7.23.13f421436a591d34fa5279b54a96ac07d70250cc8d
Vendor states this is fixed in 016b8eaca53bfd57e84ea28b5c9174c89d7679e1 (fixed)
Vendor states this is fixed in 24b3f1a9982c176d05a523a4bb9314dca0db4488 (fixed)
Vendor states this is fixed in 25b69f281cebe051a8e4ab19950a939c27ead1bc (fixed)
Vendor states this is fixed in 798ccb12810a58a37264685b28ddf990ef49559c (fixed)
Vendor states this is fixed in 9bf45feee630be868ab54e3d0f3d430c07471f0e (fixed)
Vendor states this is fixed in 9f13023607f1e95bd098cc49052b0c8955d334f9 (fixed)
Vendor states this is fixed in a762fabd7ef9a6cc07258684138f9c3f078d0326 (fixed)
Vendor states this is fixed in 3.13 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card