CVE-2026-10677

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-46446 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

The CONFIG_USERSPACE syscall verifier z_vrfy_k_poll() in kernel/poll.c allocates a kernel-side copy of the user-supplied k_poll_event[] via z_thread_malloc() and then validates each event's object handle. Before this fix, validation used K_OOPS(K_SYSCALL_OBJ(...)) inline inside the loop, which kills the calling thread without freeing events_copy.

A user thread can pass num_events >= 1 with a forged object handle to leak the allocation; because newly spawned user threads inherit the parent's resource_pool (kernel/thread.c), an attacker spawns sacrificial threads to repeat the leak until the shared kernel heap is exhausted. Once depleted, legitimate kernel allocations from that pool (k_queue alloc nodes, k_msgq buffers, future k_poll calls, etc.) fail, causing a system-level denial of service.

The fix replaces each inline K_OOPS with a conditional goto oops_free so the buffer is freed before the thread is killed. Affects Zephyr releases from v1.12.0 (when k_poll was first exposed to user mode) through v4.4.1.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 21, 2026

Last Modified

October 24, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
Fix referenced — no release confirmed yet. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Kernel heap memory leak in z_vrfy_k_poll() lets an unprivileged user thread exhaust the kernel resource pool · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r3cc-8wcr-xfj9
GitHub commit

commit 8dc7a37bc754 (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 8dc7a37bc754 — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/8dc7a37bc75402a0a3329397887f32f5fb4da3ad

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 144 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 44 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-10677?
CVE-2026-10677 is a medium-severity vulnerability; its CVE record was published on July 21, 2026. The CONFIGUSERSPACE syscall verifier zvrfykpoll() in kernel/poll.c allocates a kernel-side copy of the user-supplied kpollevent[] via zthreadmalloc() and then validates each event's object handle. Before this fix, validation used KOOPS(KSYSCALLOBJ(...)) inline inside the loop, which kills the…
When was the CVE record for CVE-2026-10677 published?
The CVE record for CVE-2026-10677 was published on July 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-10677 actively exploited?
CVE-2026-10677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10677?
CVE-2026-10677 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10677?
A fix for CVE-2026-10677 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10677

Explore →

Is Your Infrastructure Affected by CVE-2026-10677?

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