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
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 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)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
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 7× in last 7d / 30× 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 123 total refreshes for this CVE.

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 77.5% of all scored CVEs.
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.