CVE-2026-10665

{"id": "CVE-2026-10665", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-10665", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-07-13T15:48:45.958922Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "vulnerabilities@zephyrproject.org", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.4, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 5.2, "exploitabilityScore": 2.2}]}, "affected": [{"source": "vulnerabilities@zephyrproject.org", "affectedData": [{"vendor": "zephyrproject", "product": "zephyr", "versions": [{"status": "affected", "version": "4.4.0", "lessThan": "4.4.2", "versionType": "semver"}], "packageName": "zephyr", "programFiles": ["subsys/net/lib/wireguard/wg_crypto.c"], "collectionURL": "https://github.com/zephyrproject-rtos/zephyr", "defaultStatus": "unaffected"}]}], "published": "2026-07-12T17:16:24.433", "references": [{"url": "https://github.com/zephyrproject-rtos/zephyr/commit/6d8bb28dc9064e05e52b5a00b2998ecc663e38cb", "tags": ["Patch"], "source": "vulnerabilities@zephyrproject.org"}, {"url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-3wqm-wgx2-9367", "tags": ["Exploit", "Patch", "Vendor Advisory"], "source": "vulnerabilities@zephyrproject.org"}, {"url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-3wqm-wgx2-9367", "tags": ["Exploit", "Patch", "Vendor Advisory"], "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "vulnerabilities@zephyrproject.org", "description": [{"lang": "en", "value": "CWE-787"}]}], "descriptions": [{"lang": "en", "value": "In Zephyr's WireGuard subsystem (subsys/net/lib/wireguard), wg_process_data_message() in wg_crypto.c linearizes an inbound transport-data payload into a fixed pool buffer of CONFIG_WIREGUARD_BUF_LEN bytes before decryption. The call net_buf_linearize(buf->data, data_len, pkt->buffer, ..., data_len) passed the attacker-derived data_len as both the destination capacity and the copy length, defeating the function's internal len = min(len, dst_len) bound. data_len is derived from the received UDP datagram length and is only lower-bounded by wg_ctrl_recv() (no upper bound). When data_len exceeds CONFIG_WIREGUARD_BUF_LEN \u2014 e.g. when the buffer length is lowered below the link MTU, on links with MTU above the buffer size, or via reassembled IPv4/IPv6 fragments that exceed it \u2014 the underlying memcpy writes past the end of the pool buffer, an out-of-bounds write (CWE-787). The overflow occurs before the Poly1305 authentication check, so it requires only a valid receiver session index rather than a valid authenticator, and is reachable by a malicious or compromised peer (or an on-path attacker driving an established session) over the network, yielding remote memory corruption and at minimum a reliable denial of service. The defect was present in the WireGuard implementation shipped in Zephyr 4.4.0. The fix adds an explicit data_len > CONFIG_WIREGUARD_BUF_LEN rejection and corrects the linearize call to pass net_buf_max_len(buf) as the destination capacity."}, {"lang": "es", "value": "En el subsistema WireGuard de Zephyr (subsys/net/lib/wireguard), wg_process_data_message() en wg_crypto.c linealiza una carga \u00fatil de datos de transporte entrante en un b\u00fafer de grupo fijo de CONFIG_WIREGUARD_BUF_LEN bytes antes del descifrado. La llamada net_buf_linearize(buf -> data, data_len, pkt -> buffer, ..., data_len) pas\u00f3 el data_len derivado del atacante como la capacidad de destino y la longitud de copia, anulando el l\u00edmite interno de la funci\u00f3n len = min(len, dst_len). data_len se deriva de la longitud del datagrama UDP recibido y solo est\u00e1 limitado inferiormente por wg_ctrl_recv() (sin l\u00edmite superior). Cuando data_len excede CONFIG_WIREGUARD_BUF_LEN - por ejemplo, cuando la longitud del b\u00fafer se reduce por debajo de la MTU del enlace, en enlaces con MTU superior al tama\u00f1o del b\u00fafer, o a trav\u00e9s de fragmentos IPv4/IPv6 reensamblados que lo exceden - el memcpy subyacente escribe m\u00e1s all\u00e1 del final del b\u00fafer de grupo, una escritura fuera de l\u00edmites (CWE-787). El desbordamiento ocurre antes de la verificaci\u00f3n de autenticaci\u00f3n Poly1305, por lo que solo requiere un \u00edndice de sesi\u00f3n de receptor v\u00e1lido en lugar de un autenticador v\u00e1lido, y es alcanzable por un par malicioso o comprometido (o un atacante en la ruta que controla una sesi\u00f3n establecida) a trav\u00e9s de la red, lo que produce corrupci\u00f3n de memoria remota y como m\u00ednimo una denegaci\u00f3n de servicio confiable. El defecto estaba presente en la implementaci\u00f3n de WireGuard distribuida en Zephyr 4.4.0. La soluci\u00f3n a\u00f1ade un rechazo expl\u00edcito de data_len > CONFIG_WIREGUARD_BUF_LEN y corrige la llamada de linealizaci\u00f3n para pasar net_buf_max_len(buf) como la capacidad de destino."}], "lastModified": "2026-10-24T22:10:00.210", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc1:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "751E0B4E-7D5E-4847-ADD2-0A04D95A0577"}, {"criteria": "cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc2:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "CF3B04E2-F95F-42DD-BA7E-E96D4965E1D3"}, {"criteria": "cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc3:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "15D1A475-CDAB-486F-82C6-E885E844DA22"}], "operator": "OR"}]}], "sourceIdentifier": "vulnerabilities@zephyrproject.org"}