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().
Published: 2026-09-24
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Information Disclosure
Action: Apply Patch
AI Analysis

Impact

The vulnerability originates in the Linux kernel’s HSR netlink subsystem. HSR devices that reside in network namespaces other than the initial namespace broadcast netlink notifications through the default generation socket within init_net. As a result, privileged listeners in init_net receive events generated by HSR devices in any namespace. Each event carries the peer node’s MAC address and the slave port interface index (‘HSR_A_NODE_ADDR’ and ‘HSR_A_IFINDEX’). The impact is a leakage of network‑topology details to privileged users; it is not a remote code execution flaw, but it exposes internal host information to root‑level observers.

Affected Systems

Any system running a Linux kernel before the fix that includes the HSR module is affected. The bug is present regardless of the specific kernel release, as the description notes that HSR devices can live in arbitrary namespaces while the notifications are still broadcast from init_net. The vulnerability is therefore relevant to all affected Linux kernel versions until the kernel code is updated to use genlmsg_multicast_netns() for HSR notifications.

Risk and Exploitability

Exploitation requires a privileged process capable of listening to netlink messages in the init_net namespace; non‑privileged users cannot trigger the netlink broadcast. The CVSS score of 5.5 indicates a moderate severity and the EPSS score of < 1% suggests a low exploitation probability. The vulnerability is not listed in CISA KEV, indicating no confirmed public exploitation. Nonetheless, any root user can glean additional network information from other namespaces, which can aid further attacks. The moderate risk level reflects the information disclosure to privileged users rather than a privilege escalation or remote attack vector.

Generated by OpenCVE AI on October 1, 2026 at 18:37 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that contains the HSR netlink notification fix, ensuring genlmsg_multicast_netns() is used instead of genlmsg_multicast().
  • If a kernel update cannot be applied immediately, restrict HSR usage to the intended namespaces or unload the HSR module when it is not required, thereby limiting cross‑namespace notifications.
  • Continuously monitor system logs for unexpected HSR netlink events and coordinate with kernel maintainers to receive future security advisories.

Generated by OpenCVE AI on October 1, 2026 at 18:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4817-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4841-1 linux security update
Debian DSA Debian DSA DSA-6528-1 linux security update
History

Sat, 03 Oct 2026 11:15:00 +0000


Thu, 01 Oct 2026 16:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200

Tue, 29 Sep 2026 13:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-941
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Fri, 25 Sep 2026 02:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200

Thu, 24 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
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().
Title hsr: broadcast netlink notifications in the device's net namespace
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-03T10:58:11.119Z

Reserved: 2026-09-24T14:53:16.868Z

Link: CVE-2026-97419

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-24T17:17:19.733

Modified: 2026-10-03T11:17:54.000

Link: CVE-2026-97419

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-24T00:00:00Z

Links: CVE-2026-97419 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-01T18:45:06Z

Weaknesses
  • CWE-941

    Incorrectly Specified Destination in a Communication Channel