CVE-2026-97419

UnknownEPSS 0.17%

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(). EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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().

Metrics

EPSS Probability
0.17%

5.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= f421436a591d34fa5279b54a96ac07d70250cc8d, < 9f13023607f1e95bd098cc49052b0c8955d334f9; >= f421436a591d34fa5279b54a96ac07d70250cc8d, < 798ccb12810a58a37264685b28ddf990ef49559c; >= f421436a591d34fa5279b54a96ac07d70250cc8d, < 9bf45feee630be868ab54e3d0f3d430c07471f0e; >= f421436a591d34fa5279b54a96ac07d70250cc8d, < 016b8eaca53bfd57e84ea28b5c9174c89d7679e1; >= f421436a591d34fa5279b54a96ac07d70250cc8d, < 25b69f281cebe051a8e4ab19950a939c27ead1bc; >= f421436a591d34fa5279b54a96ac07d70250cc8d, < 24b3f1a9982c176d05a523a4bb9314dca0db4488; >= f421436a591d34fa5279b54a96ac07d70250cc8d, < a762fabd7ef9a6cc07258684138f9c3f078d0326
LinuxLinux3.13

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97419?
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().
How severe is CVE-2026-97419?
Severity scoring for CVE-2026-97419 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-97419?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-97419?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST