CVE-2026-53214

MEDIUMNVD 5.55.5—
EchelonGraph scoreHIGH 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
Trending — 5 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 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(high)
EPSS
2.3%
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 34× 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.

  1. 2026-07-07 00:10 UTCEG score recompute
  2. 2026-07-07 00:10 UTCVendor advisory
  3. 2026-07-07 00:10 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-05 22:03 UTCEG score recompute
  7. 2026-07-05 22:03 UTCVendor advisory
  8. 2026-07-05 22:03 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 19:56 UTCEG score recompute
  12. 2026-07-04 19:56 UTCVendor advisory
  13. 2026-07-04 19:56 UTCGHSA enrichment
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 17:50 UTCEG score recompute▲ 5.50
  17. 2026-07-03 17:50 UTCVendor advisory
  18. 2026-07-03 17:49 UTCGHSA enrichment
  19. 2026-07-02 22:05 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 23:15 UTCVendor advisory
  23. 2026-06-30 23:15 UTCGHSA enrichment
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 9 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 04:41 UTCEG score recompute
  5. 2026-06-28 04:41 UTCGHSA enrichment
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 10:07 UTCEG score recompute
  9. 2026-06-25 10:07 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

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 2.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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