CVE-2026-97419
Last modified
CVE-2026-97419 is a vulnerability of currently unknown severity. 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().
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= f421436a591d34fa5279b54a96ac07d70250cc8d, < 25b69f281cebe051a8e4ab19950a939c27ead1bc; >= f421436a591d34fa5279b54a96ac07d70250cc8d, < 24b3f1a9982c176d05a523a4bb9314dca0db4488; >= f421436a591d34fa5279b54a96ac07d70250cc8d, < a762fabd7ef9a6cc07258684138f9c3f078d0326 |
| Linux | Linux | 3.13 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-97419?
How severe is CVE-2026-97419?
How do I fix CVE-2026-97419?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-97413In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-97414In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97415In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-97416In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97417In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-97418In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9742When OIDC authentication is enabled in configuration, client…5.9
- CVE-2026-97420In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97421In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-97422In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97423In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97424In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-97419?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
