CVE-2026-10657 Details
Description
Zephyr's DNS resolver detects mDNS (.local) queries in dns_resolve_name_internal() (subsys/net/lib/dns/resolve.c) with memcmp(strrchr(query, '.'), ".local", 7), which always reads a fixed 7 bytes from the suffix pointer. When the resolved hostname's final label is shorter than 7 bytes (e.g. names ending in .org, .com, .net, .io, or a trailing dot), the comparison reads 1-2 bytes past the string's NUL terminator. The hostname (query) is the caller-supplied name passed through the standard getaddrinfo()/dns_get_addr_info()/dns_resolve_name() path and is influenceable by operators or remote inputs (server names from configuration, parsed URLs, or app-facing interfaces). On a tightly-sized buffer with no slack (for example a userspace getaddrinfo call where the hostname is copied with k_usermode_string_alloc_copy to exactly strlen+1 bytes), the over-read crosses the allocation boundary; if that boundary is unmapped (guard page, memory-domain boundary under MPU, or an address sanitizer) the over-read faults, causing a denial of service. The over-read bytes are never returned, so there is no information disclosure. The flaw is compiled only when CONFIG_MDNS_RESOLVER is enabled, exists since v1.10.0, and is fixed by replacing the fixed-length memcmp with a NUL-safe strcmp(ptr, ".local").
A vulnerability exists in the Zephyr operating system's DNS resolver, specifically in how it handles multicast DNS (mDNS) queries. The issue arises in the function 'dns_resolve_name_internal' within the file 'subsys/net/lib/dns/resolve.c'. When the resolver checks for mDNS suffixes by comparing the last label of a hostname to '.local', it uses 'memcmp' to read a fixed 7 bytes. This approach can lead to an out-of-bounds read if the hostname's final label is shorter than 7 bytes, such as those ending in common top-level domains or a trailing dot. The vulnerability is triggered when the DNS resolver processes user-supplied hostnames, which can be influenced by remote inputs or operator configurations. In scenarios where the hostname is copied into a tightly-sized buffer with no extra space, the over-read can cross into memory that is unmapped, potentially causing a fault and leading to a denial-of-service condition. Notably, this over-read does not result in any information disclosure, as the excess bytes are not returned to the caller.
Users can upgrade to Zephyr version 4.5.0 or later, where this vulnerability has been fixed. Instructions for upgrading can be found in the Zephyr project documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 6, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-125 | Out-of-bounds Read | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| zephyrproject zephyr | >= 1.10.0, <= 4.4.0 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 25, 2026 | CVE Translated | [email protected] |
| Oct 15, 2026 | CVE Modified | [email protected] |
| Jul 14, 2026 | CVE Modified | [email protected] |
| Jul 8, 2026 | Initial Analysis | [email protected] |
| Jul 6, 2026 | CVE Modified | CISA-ADP |
| Jul 5, 2026 | New CVE Received | [email protected] |