Quick answers
- Is CVE-2026-10677 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10677 being exploited in the wild.
- How severe is CVE-2026-10677?
- Medium severity, with a CVSS score of 6.5, published 21 July 2026.
- Which products and versions are affected?
- Zephyr Project Zephyr OS v1.12.0 to v4.4.1.
- Is there a fix for CVE-2026-10677?
- A patch was published on 2026-07-21: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-10677 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-10677?
- Check whether you run Zephyr Project Zephyr OS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A memory leak exists in the z_vrfy_k_poll() syscall verifier in kernel/poll.c. The function allocates a kernel-side copy of user-supplied poll events using z_thread_malloc(), but fails to free this memory if validation of an object handle fails. Specifically, the use of the K_OOPS macro inside the validation loop terminates the calling thread immediately without executing cleanup code. Because child threads inherit the parent's resource_pool, an attacker can spawn multiple threads to repeatedly trigger this leak, eventually exhausting the kernel heap. This prevents subsequent kernel allocations for queues, messages, or other system calls, leading to a permanent denial of service until reboot. The issue is fixed in version 4.5.0 by ensuring memory is freed before the thread is terminated.
Affected products
- Zephyr Project Zephyr OS v1.12.0 to v4.4.1
Timeline
- 2026-07-19: other: Embargo date
- 2026-07-21: disclosed: Advisory published by Zephyr Project
- 2026-07-21: patched: Fix merged into main branch