In the Linux kernel, the following vulnerability has been resolved: hsr: broadcast netlink...
🔗 CVE IDs covered (1)
📋 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().
🔗 References (9)
- https://nvd.nist.gov/vuln/detail/CVE-2026-97419
- https://git.kernel.org/stable/c/24b3f1a9982c176d05a523a4bb9314dca0db4488
- https://git.kernel.org/stable/c/25b69f281cebe051a8e4ab19950a939c27ead1bc
- https://git.kernel.org/stable/c/a762fabd7ef9a6cc07258684138f9c3f078d0326
- https://git.kernel.org/stable/c/016b8eaca53bfd57e84ea28b5c9174c89d7679e1
- https://git.kernel.org/stable/c/798ccb12810a58a37264685b28ddf990ef49559c
- https://git.kernel.org/stable/c/9bf45feee630be868ab54e3d0f3d430c07471f0e
- https://git.kernel.org/stable/c/9f13023607f1e95bd098cc49052b0c8955d334f9
- https://github.com/advisories/GHSA-v886-hjg7-fghx