Technical impact
The vulnerability is an out‑of‑bounds read in the SOCKS5 client of Zephyr’s networking stack. The CONNECT request builder incorrectly selects the address type from the proxy’s family while reading bytes from the destination address. When an IPv6 proxy is used with an IPv4 destination, the code treats a 16‑byte IPv6 address as a 12‑byte IPv4 structure, copying 12 bytes past the end of the destination object and exposing stale kernel‑stack data to the SOCKS5 proxy. The leak is limited to 12 bytes per connect() call and provides only information disclosure; no writable or privileged escalation primitive exists.
Affected Systems
Zephyr Project Zephyr RTOS builds that enable CONFIG_SOCKS, contain SOCKS5 support, and compile with both IPv4 and IPv6 networking enabled. Any image where the configuration option CONFIG_SOCKS is set and a user can set the SO_SOCKS5 socket option may be affected.
Risk and Exploitability
The CVSS score of 3.3 indicates low overall severity. EPSS data is not available and the vulnerability is not listed in the CISA KEV catalog, suggesting limited current exploitation evidence. An attacker must control a SOCKS5 proxy and have a user‑mode thread that can send a connect request with a mismatched address family. The attack vector is therefore local or remote but requires attacker control of the proxy; the exposure would be to the proxy operator rather than to an external target.