Impact
A flaw in Zephyr’s SocketCAN implementation allows a user to send a frame that is shorter than the expected socketcan_frame structure. When assertions are disabled, the code fails to check the provided length before dereferencing fields beyond the buffer. This out‐of‐bounds read can crash the kernel or, if the parsed frame is sent onto the network, leak adjacent memory containing sensitive information. The primary impact is a denial of service with potential confidentiality exposure.
Affected Systems
Zephyr RTOS is affected. No specific version range is listed, but the vulnerability is tied to the SocketCAN component of the Zephyr project.
Risk and Exploitability
The CVSS score of 6.1 indicates moderate severity. EPSS data is not available, and the flaw is not listed in the CISA KEV catalog. The likely attack vector is local; an attacker with the ability to invoke the sendto syscall on the CAN device can provide custom frame data, triggering the vulnerability. Exploitation does not require elevated privileges beyond those normally needed to write to the CAN interface.
OpenCVE Enrichment