CVE-2026-53214

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-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:

ipv6: Fix a potential NPD in cleanup_prefix_route()

addrconf_get_prefix_route() can return the fib6_null_entry sentinel entry which has a NULL fib6_table pointer. Therefore, before setting the route's expiration time, check that we are not working with this entry, as otherwise a NPD will be triggered [1].

Note that the other callers of addrconf_get_prefix_route() are not susceptible to this bug:

  • addrconf_prefix_rcv(): Requests a route with the 'RTF_ADDRCONF |
RTF_PREFIX_RT' flags which are not set on fib6_null_entry.
  • modify_prefix_route(): Fixed by commit a747e02430df ("ipv6: avoid
possible NULL deref in modify_prefix_route()").
  • __ipv6_ifa_notify(): Calls ip6_del_rt() which specifically checks for
fib6_null_entry and returns an error.

[1] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037] [...] Call Trace:

__kasan_check_byte (mm/kasan/common.c:573) lock_acquire.part.0 (kernel/locking/lockdep.c:5842 (discriminator 1)) _raw_spin_lock_bh (kernel/locking/spinlock.c:182 (discriminator 1)) cleanup_prefix_route (net/ipv6/addrconf.c:1280) ipv6_del_addr (net/ipv6/addrconf.c:1342) inet6_addr_del.isra.0 (net/ipv6/addrconf.c:3119) inet6_rtm_deladdr (net/ipv6/addrconf.c:4812) rtnetlink_rcv_msg (net/core/rtnetlink.c:6997) netlink_rcv_skb (net/netlink/af_netlink.c:2555) netlink_unicast (net/netlink/af_netlink.c:1344) netlink_sendmsg (net/netlink/af_netlink.c:1899) __sock_sendmsg (net/socket.c:802 (discriminator 4)) ____sys_sendmsg (net/socket.c:2698) ___sys_sendmsg (net/socket.c:2752) __sys_sendmsg (net/socket.c:2784) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)

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
6%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (5)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic

ipv6: Fix a potential NPD in cleanup_prefix_route() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: Fix a potential NPD in cleanup_prefix_route() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/653a2849305708f75260b5296f17b2a759ff9cc7
generic

ipv6: Fix a potential NPD in cleanup_prefix_route() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f82b02b4059ddc06e4fcfd057bfb59fd6885cd2
generic

ipv6: Fix a potential NPD in cleanup_prefix_route() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/192df376a05c2db15564640f9da7e20907c1fa24
generic

ipv6: Fix a potential NPD in cleanup_prefix_route() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07d9a0870a178843cea44cfd58c27445dc94cf5f

Vendor Advisories for CVE-2026-53214(2)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 60× 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 188 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53214?
CVE-2026-53214 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: Fix a potential NPD in cleanupprefixroute() addrconfgetprefixroute() can return the fib6null_entry sentinel entry which has a NULL fib6_table pointer. Therefore, before setting the route's expiration time, check that we are…
When was CVE-2026-53214 disclosed?
CVE-2026-53214 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53214 actively exploited?
CVE-2026-53214 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 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53214?
CVE-2026-53214 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53214?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53214, 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-53214

Explore →

Is Your Infrastructure Affected by CVE-2026-53214?

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

Start Free Scan →Browse All CVEs