CVE-2026-23300

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-03-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop

When a standalone IPv6 nexthop object is created with a loopback device (e.g., "ip -6 nexthop add id 100 dev lo"), fib6_nh_init() misclassifies it as a reject route. This is because nexthop objects have no destination prefix (fc_dst=::), causing fib6_is_reject() to match any loopback nexthop. The reject path skips fib_nh_common_init(), leaving nhc_pcpu_rth_output unallocated. If an IPv4 route later references this nexthop, __mkroute_output() dereferences NULL nhc_pcpu_rth_output and panics.

Simplify the check in fib6_nh_init() to only match explicit reject routes (RTF_REJECT) instead of using fib6_is_reject(). The loopback promotion heuristic in fib6_is_reject() is handled separately by ip6_route_info_create_nh(). After this change, the three cases behave as follows:

  • Explicit reject route ("ip -6 route add unreachable 2001:db8::/64"):
RTF_REJECT is set, enters reject path, skips fib_nh_common_init(). No behavior change.
  • Implicit loopback reject route ("ip -6 route add 2001:db8::/32 dev lo"):
RTF_REJECT is not set, takes normal path, fib_nh_common_init() is called. ip6_route_info_create_nh() still promotes it to reject afterward. nhc_pcpu_rth_output is allocated but unused, which is harmless.
  • Standalone nexthop object ("ip -6 nexthop add id 100 dev lo"):
RTF_REJECT is not set, takes normal path, fib_nh_common_init() is called. nhc_pcpu_rth_output is properly allocated, fixing the crash when IPv4 routes reference this nexthop.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

March 25, 2026

Last Modified

July 14, 2026

Advisory Details (10)

Auto-updated Jul 17, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic🔴 Active Exploitation

SSA-082556

https://cert-portal.siemens.com/productcert/html/ssa-082556.html
generic

SSA-019113

https://cert-portal.siemens.com/productcert/html/ssa-019113.html
generic

net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f7c9f8e3607440fe39300efbaf46cf7b5eecb23f
generic

net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c11d7c56c2076ee9cd72004f1976fe0734df2ae9
generic

net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b5062fc2150614c9ea8a611c2e0cb6e047ebfa3a
generic

net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b3b5a037d520afe3d5276e653bc0ff516bbda34c
generic

net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b299121e7453d23faddf464087dff513a495b4fc
generic

net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8650db85b4259d2885d2a80fbc2317ce24194133
generic

net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/607e68c1b7c5a30c795571be1906d716e989a644
generic

net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21ec92774d1536f71bdc90b0e3d052eff99cf093

Vendor Advisories for CVE-2026-23300(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv
linuxKernel @ 6.1.167—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (117 versions)6.19.8-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 206 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 15:01 UTCOSV refresh
  3. 2026-09-02 14:11 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:48 UTCEPSS rescore
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 17:03 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 10:26 UTCEG score recompute
  20. 2026-08-16 10:26 UTCVendor advisory
  21. 2026-08-16 10:26 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 06:45 UTCEG score recompute
  25. 2026-08-14 06:45 UTCVendor advisory
Show 75 more
  1. 2026-08-14 06:45 UTCGHSA enrichment
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-12 20:59 UTCEG score recompute
  4. 2026-08-12 20:59 UTCVendor advisory
  5. 2026-08-12 20:59 UTCGHSA enrichment
  6. 2026-08-12 13:50 UTCEPSS rescore
  7. 2026-08-11 13:42 UTCEPSS rescore
  8. 2026-08-11 04:05 UTCEG score recompute
  9. 2026-08-11 04:05 UTCVendor advisory
  10. 2026-08-11 04:05 UTCGHSA enrichment
  11. 2026-08-11 00:00 UTCEPSS rescore
  12. 2026-08-10 04:53 UTCEG score recompute
  13. 2026-08-10 04:53 UTCVendor advisory
  14. 2026-08-10 04:53 UTCGHSA enrichment
  15. 2026-08-09 13:46 UTCEPSS rescore
  16. 2026-08-09 06:20 UTCEG score recompute
  17. 2026-08-09 06:20 UTCVendor advisory
  18. 2026-08-09 06:20 UTCGHSA enrichment
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-07 16:37 UTCEG score recompute
  21. 2026-08-07 16:37 UTCVendor advisory
  22. 2026-08-07 16:37 UTCGHSA enrichment
  23. 2026-08-06 13:46 UTCEPSS rescore
  24. 2026-08-06 01:06 UTCEG score recompute
  25. 2026-08-06 01:06 UTCVendor advisory
  26. 2026-08-06 01:06 UTCGHSA enrichment
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-04 10:38 UTCEPSS rescore
  30. 2026-08-03 23:51 UTCEG score recompute
  31. 2026-08-03 23:51 UTCVendor advisory
  32. 2026-08-03 23:51 UTCGHSA enrichment
  33. 2026-08-03 10:35 UTCEPSS rescore
  34. 2026-08-02 15:40 UTCEG score recompute
  35. 2026-08-02 15:40 UTCVendor advisory
  36. 2026-08-02 15:40 UTCGHSA enrichment
  37. 2026-08-02 02:26 UTCEPSS rescore
  38. 2026-08-01 04:15 UTCEPSS rescore
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-27 14:13 UTCEPSS rescore
  41. 2026-07-26 14:54 UTCEPSS rescore
  42. 2026-07-26 14:54 UTCEPSS rescore
  43. 2026-07-25 14:17 UTCEPSS rescore
  44. 2026-07-25 14:17 UTCEPSS rescore
  45. 2026-07-24 14:17 UTCEPSS rescore
  46. 2026-07-23 14:18 UTCEPSS rescore
  47. 2026-07-23 14:18 UTCEPSS rescore
  48. 2026-07-23 03:06 UTCEG score recompute
  49. 2026-07-22 14:08 UTCEPSS rescore
  50. 2026-07-21 15:24 UTCEPSS rescore
  51. 2026-07-21 15:24 UTCEPSS rescore
  52. 2026-07-20 17:08 UTCEPSS rescore
  53. 2026-07-19 14:31 UTCEPSS rescore
  54. 2026-07-19 14:31 UTCEPSS rescore
  55. 2026-07-19 02:29 UTCEPSS rescore
  56. 2026-07-19 02:28 UTCEPSS rescore
  57. 2026-07-18 10:04 UTCEPSS rescore
  58. 2026-07-18 10:04 UTCEPSS rescore
  59. 2026-07-17 07:16 UTCOSV refresh
  60. 2026-07-16 17:03 UTCEPSS rescore
  61. 2026-07-16 17:03 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 16:57 UTCEPSS rescore
  64. 2026-07-15 02:00 UTCEPSS rescore
  65. 2026-07-15 02:00 UTCEPSS rescore
  66. 2026-07-14 13:19 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  67. 2026-07-14 13:11 UTCMITRE cvelistV5
  68. 2026-07-13 22:30 UTCEPSS rescore
  69. 2026-07-13 06:13 UTCEPSS rescore
  70. 2026-07-13 06:13 UTCEPSS rescore
  71. 2026-07-12 05:46 UTCEPSS rescore
  72. 2026-07-12 05:46 UTCEPSS rescore
  73. 2026-07-11 08:27 UTCEPSS rescore
  74. 2026-07-09 19:10 UTCEPSS rescore
  75. 2026-07-08 15:15 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-23300?
CVE-2026-23300 is a medium vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop When a standalone IPv6 nexthop object is created with a loopback device (e.g., "ip -6 nexthop add id 100 dev lo"), fib6nhinit() misclassifies it as a reject…
When was CVE-2026-23300 disclosed?
CVE-2026-23300 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23300 actively exploited?
CVE-2026-23300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-23300?
CVE-2026-23300 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23300, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23300

Explore →

Is Your Infrastructure Affected by CVE-2026-23300?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs