cve.bz

CVE-2026-97419 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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().
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.271
  • Linux Linux: fixed in 5.15.222
  • Linux Linux: fixed in 6.1.189
  • Linux Linux: fixed in 6.6.158
  • Linux Linux: fixed in 6.12.111
  • Linux Linux: fixed in 6.18.53
  • Linux Linux: fixed in 7.2
  • Debian, Ubuntu, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-97419 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97419?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97419?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97419 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux3.13 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.271
Linux5.155.15.222
Linux6.16.1.189
Linux6.66.6.158
Linux6.126.12.111
Linux6.186.18.53
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.190-1DEBIAN-CVE-2026-97419
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-97419
Debian13linux6.12.111-1DEBIAN-CVE-2026-97419
Debian14linux7.2.6-1DEBIAN-CVE-2026-97419
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-97419
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-97419
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-97419
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-97419 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-97419 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-97419 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-97419 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-97419 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-97419 USN-8962-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-97419 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-97419 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-97419 USN-9024-1
82 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernel6.6.158.1-1AZL-103916
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-97419
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-97419
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-97419

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate severity flaw was found in the Linux kernel High-availability Seamless Redundancy (HSR) subsystem. The HSR generic netlink family permits HSR devices to exist in network namespaces other than the initial namespace, but the asynchronous ring error (hsr_nl_ringerror) and node down (hsr_nl_nodedown) notifiers broadcast their notifications only to the initial (root) network namespace via genlmsg_multicast(), regardless of the device's own namespace. As a result, a local user able to listen in the initial network namespace could observe ring error and node down notifications for HSR devices in other namespaces, exposing limited network metadata such as peer node MAC addresses (HSR_A_NODE_ADDR) and slave port interface indices (HSR_A_IFINDEX), while listeners in the device's own namespace never received these status events. Red Hat Enterprise Linux 9 and 10, Red Hat In-Vehicle OS 2, and OpenShift Container Platform releases based on RHEL CoreOS 9 are affected; the fix is currently deferred for these products, and the residual risk is limited to local cross-namespace disclosure of network metadata and to missing HSR status notifications within the device's namespace. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those releases.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-97419.

References

Check your stackJSON