Kernel warning via missing network namespace
Published Oct 23, 2026 · Updated Oct 23, 2026
Namespace handling in Linux IPv6 segment routing allows local users to trigger a kernel warning via TIPC discovery traffic. The seg6_make_flowlabel() function calls skb_get_hash() without supplying its network namespace when the packet has neither a device nor a socket. The documented trigger requires administrative bearer configuration, an IPv4 route using segment-routing encapsulation, and net.ipv6.seg6_flowlabel set to 1; no crash or privilege escalation is demonstrated.
Summary
What happened
Namespace handling in Linux IPv6 segment routing allows local users to trigger a kernel warning via TIPC discovery traffic. The seg6_make_flowlabel() function calls skb_get_hash() without supplying its network namespace when the packet has neither a device nor a socket. The documented trigger requires administrative bearer configuration, an IPv4 route using segment-routing encapsulation, and net.ipv6.seg6_flowlabel set to 1; no crash or privilege escalation is demonstrated.
The record
- CVE
- CVE-2026-98934
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.20
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <086e8acb3a0e55f6d22d29fae2a4a3b1561bb766
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <4ab37e4f4a33c64d9e565dc8c4c3ed774f05c0e3
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <53b21bc2df6e8ed538bceda93a5104a5fe6a8a84
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <8ec454dcd00ce3375119111c6394964455b36d0d
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <8fe3d6717f5536793727e60b7a0b7ec20c697def
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- syzkaller C reproducer for WARNING in __skb_flow_dissectproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us