CVE-2026-10637

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 4 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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

subsys/net/ip/ipv6_mld.c:mld_send() read the packet interface via net_pkt_iface(pkt) after net_send_data(pkt) returned successfully. Per the network stack's ownership contract (include/zephyr/net/net_core.h, and the explicit warning in subsys/net/ip/net_core.c:453-460 'do not use pkt after that call'), a successful send transfers ownership of the net_pkt and the L2 driver frees it (e.g. ethernet_send() unrefs the packet on success, subsys/net/l2/ethernet/ethernet.c:790), returning it to its k_mem_slab.

The subsequent net_pkt_iface(pkt) is therefore a read of a freed object; the recovered interface pointer is then dereferenced and incremented by the per-interface statistics path (net_stats.h UPDATE_STAT/SET_STAT) when CONFIG_NET_STATISTICS_PER_INTERFACE is enabled. If the freed slot is concurrently reallocated, pkt->iface may read back as NULL (NULL-pointer dereference / crash) or as a stale/garbage pointer (stray increment write / memory corruption).

The path is reachable remotely on the local link without authentication: handle_mld_query() (registered for NET_ICMPV6_MLD_QUERY) responds to a valid MLDv2 General Query (unspecified multicast address, hop limit 1) by calling send_mld_report() -> mld_send().

The result is a remotely triggerable denial of service of the networking stack, with a narrow possibility of memory corruption. The fix caches the interface in a local before sending and no longer touches the packet after net_send_data(). The IPv4/IGMP sibling (igmp_send) already used the corrected pattern.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
21.8%
KEV
Not listed

Published

June 16, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jun 16, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Use-after-free of net_pkt in IPv6 MLD send path triggerable by a link-local MLD Query · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-m23w-34pp-4h92
github_commit

commit 3159c53e8e7d (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 3159c53e8e7d — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/3159c53e8e7d233c2a85a0798cf25ac441db6dae

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 81× 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-16 02:34 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 15:29 UTCEG score recompute
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 01:18 UTCEG score recompute
  6. 2026-07-14 19:21 UTCNVD updateCVSS v3 → 7.1 · severity → HIGH
  7. 2026-07-14 19:00 UTCMITRE cvelistV5CVSS v3 → 5.9 · severity → MEDIUM
  8. 2026-07-14 13:00 UTCEG score recompute
  9. 2026-07-14 01:54 UTCEG score recompute
  10. 2026-07-13 22:30 UTCEPSS rescore
  11. 2026-07-13 14:47 UTCEG score recompute
  12. 2026-07-13 06:12 UTCEPSS rescore
  13. 2026-07-13 03:35 UTCEG score recompute
  14. 2026-07-12 16:20 UTCEG score recompute
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 05:11 UTCEG score recompute
  17. 2026-07-11 18:03 UTCEG score recompute
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 06:56 UTCEG score recompute
  20. 2026-07-10 19:44 UTCEG score recompute
  21. 2026-07-10 08:38 UTCEG score recompute
  22. 2026-07-09 19:55 UTCEG score recompute
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 08:08 UTCEG score recompute
  25. 2026-07-08 21:02 UTCEG score recompute
Show 56 more
  1. 2026-07-08 09:57 UTCEG score recompute
  2. 2026-07-07 22:52 UTCEG score recompute
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-07 11:46 UTCEG score recompute
  5. 2026-07-06 23:14 UTCEG score recompute
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 21:26 UTCEG score recompute
  9. 2026-07-05 10:20 UTCEG score recompute
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-04 23:06 UTCEG score recompute
  13. 2026-07-04 12:01 UTCEG score recompute
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 00:55 UTCEG score recompute
  16. 2026-07-03 13:49 UTCEG score recompute
  17. 2026-07-03 00:37 UTCEG score recompute
  18. 2026-07-02 13:25 UTCEG score recompute
  19. 2026-07-02 02:01 UTCEG score recompute 1.20
  20. 2026-07-02 01:19 UTCNVD updateCVSS v3 → 7.1 · severity → HIGH
  21. 2026-07-01 15:06 UTCEPSS rescore
  22. 2026-07-01 15:06 UTCEPSS rescore
  23. 2026-07-01 01:27 UTCEG score recompute
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-30 00:45 UTCEG score recompute
  26. 2026-06-29 14:06 UTCEPSS rescore
  27. 2026-06-29 00:11 UTCEG score recompute
  28. 2026-06-28 14:07 UTCEPSS rescore
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-28 04:56 UTCEPSS rescore
  31. 2026-06-27 23:37 UTCEG score recompute
  32. 2026-06-27 03:08 UTCEPSS rescore
  33. 2026-06-26 23:02 UTCEG score recompute
  34. 2026-06-25 22:28 UTCEG score recompute
  35. 2026-06-25 13:49 UTCEPSS rescore
  36. 2026-06-24 21:53 UTCEG score recompute
  37. 2026-06-24 14:05 UTCEPSS rescore
  38. 2026-06-23 21:32 UTCEPSS rescore
  39. 2026-06-23 21:19 UTCEG score recompute
  40. 2026-06-22 20:45 UTCEG score recompute
  41. 2026-06-22 14:25 UTCEPSS rescore
  42. 2026-06-22 14:25 UTCEPSS rescore
  43. 2026-06-21 20:10 UTCEG score recompute
  44. 2026-06-21 14:56 UTCEPSS rescore
  45. 2026-06-21 14:56 UTCEPSS rescore
  46. 2026-06-21 01:59 UTCEPSS rescore
  47. 2026-06-21 01:59 UTCEPSS rescore
  48. 2026-06-20 19:26 UTCEG score recompute
  49. 2026-06-19 19:25 UTCEPSS rescore
  50. 2026-06-19 18:21 UTCEG score recompute
  51. 2026-06-18 17:52 UTCEPSS rescore
  52. 2026-06-18 17:45 UTCEG score recompute
  53. 2026-06-17 17:53 UTCEPSS rescore
  54. 2026-06-17 16:52 UTCEG score recompute
  55. 2026-06-16 15:48 UTCEG score recompute
  56. 2026-06-16 15:47 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-10637?
CVE-2026-10637 is a high vulnerability published on June 16, 2026. subsys/net/ip/ipv6mld.c:mldsend() read the packet interface via netpktiface(pkt) after netsenddata(pkt) returned successfully. Per the network stack's ownership contract (include/zephyr/net/netcore.h, and the explicit warning in subsys/net/ip/netcore.c:453-460 'do not use pkt after that call'), a…
When was CVE-2026-10637 disclosed?
CVE-2026-10637 was first published in the National Vulnerability Database on June 16, 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-10637 actively exploited?
CVE-2026-10637 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10637?
CVE-2026-10637 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-10637?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10637, 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-10637

Explore →

Is Your Infrastructure Affected by CVE-2026-10637?

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