CVE-2026-97419: hsr: broadcast netlink notifications in the device's net namespace
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 016b8eaca53bfd57e84ea28b5c9174c89d7679e1, 24b3f1a9982c176d05a523a4bb9314dca0db4488, 25b69f281cebe051a8e4ab19950a939c27ead1bc; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 016b8eaca53bfd57e84ea28b5c9174c89d7679e1, 24b3f1a9982c176d05a523a4bb9314dca0db4488, 25b69f281cebe051a8e4ab19950a939c27ead1bc; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Sep 24, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.13affected
- f421436a591d34fa5279b54a96ac07d70250cc8d and later · before 9f13023607f1e95bd098cc49052b0c8955d334f9affected · git
- f421436a591d34fa5279b54a96ac07d70250cc8d and later · before 798ccb12810a58a37264685b28ddf990ef49559caffected · git
- f421436a591d34fa5279b54a96ac07d70250cc8d and later · before 9bf45feee630be868ab54e3d0f3d430c07471f0eaffected · git
- f421436a591d34fa5279b54a96ac07d70250cc8d and later · before 016b8eaca53bfd57e84ea28b5c9174c89d7679e1affected · git
- f421436a591d34fa5279b54a96ac07d70250cc8d and later · before 25b69f281cebe051a8e4ab19950a939c27ead1bcaffected · git
- f421436a591d34fa5279b54a96ac07d70250cc8d and later · before 24b3f1a9982c176d05a523a4bb9314dca0db4488affected · git
- f421436a591d34fa5279b54a96ac07d70250cc8d and later · before a762fabd7ef9a6cc07258684138f9c3f078d0326affected · git
- before 3.13not affected · semver
- 5.10.271 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97417Sep 24, 2026 · netfilter: nf_conntrack: use get_unaligned_be32() in tcp_sack()30Monitor
- ← EarlierCVE-2026-97418Sep 24, 2026 · ALSA: es18xx: check control allocation before private data setup0Monitor
- Later →CVE-2026-97420Sep 24, 2026 · bpf: NUL-terminate replaced sysctl value0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 016b8eaca53bfd57e84ea28b5c9174c89d7679e1 | Vendor (CNA) |
| Linux Linux | 24b3f1a9982c176d05a523a4bb9314dca0db4488 | Vendor (CNA) |
| Linux Linux | 25b69f281cebe051a8e4ab19950a939c27ead1bc | Vendor (CNA) |
| Linux Linux | 798ccb12810a58a37264685b28ddf990ef49559c | Vendor (CNA) |
| Linux Linux | 9bf45feee630be868ab54e3d0f3d430c07471f0e | Vendor (CNA) |
| Linux Linux | 9f13023607f1e95bd098cc49052b0c8955d334f9 | Vendor (CNA) |
| Linux Linux | a762fabd7ef9a6cc07258684138f9c3f078d0326 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/24b3f1a9982c176d05a523a4bb9314dca0db4488
- git.kernel.org/stable/c/25b69f281cebe051a8e4ab19950a939c27ead1bc
- git.kernel.org/stable/c/798ccb12810a58a37264685b28ddf990ef49559c
- git.kernel.org/stable/c/9bf45feee630be868ab54e3d0f3d430c07471f0e
- git.kernel.org/stable/c/9f13023607f1e95bd098cc49052b0c8955d334f9
- git.kernel.org/stable/c/a762fabd7ef9a6cc07258684138f9c3f078d0326
Vendor advisories and official records. Exploit/PoC links are deliberately left out.