Loading vulnerability…
CVE-2026-23300 is a Linux kernel networking vulnerability in the IPv6 route/nexthop initialization path. A standalone IPv6 nexthop object created on the loopback device, for example via "ip -6 nexthop add id 100 dev lo", is incorrectly classified by fib6_nh_init() as a reject route because nexthop objects have no destination prefix (fc_dst=::) and fib6_is_reject() matches loopback nexthops in that case. As a result, execution takes the reject path and skips fib_nh_common_init(), leaving nhc_pcpu_rth_output unallocated. If an IPv4 route later references that nexthop, __mkroute_output() dereferences the NULL nhc_pcpu_rth_output pointer, causing a kernel panic. The fix changes fib6_nh_init() so that only explicit reject routes marked with RTF_REJECT take the reject path; loopback reject promotion remains handled separately by ip6_route_info_create_nh().
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Referenced as one of many CVEs addressed by SUSE kernel security updates; no vulnerability details are provided in the content.
Listed as one of 206 vulnerabilities addressed by a SUSE kernel security update; no per-CVE technical detail is provided in the content.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.