Home

Description

The SocketCAN implementation validates the length of a user-provided buffer containing a socketcan_frame object using only a NET_ASSERT statement in zcan_sendto_ctx() before dereferencing it in socketcan_to_can_frame(). In production builds where assertions are disabled, a userspace application that controls the length passed to a sendto syscall can supply an incomplete or truncated frame, causing socketcan_to_can_frame() to dereference fields beyond the end of the buffer. This results in an out-of-bounds read that can cause denial-of-service crashes or, because the parsed frame contents are transmitted on the network, leak adjacent memory.

PUBLISHED Reserved 2026-03-27 | Published 2026-05-30 | Updated 2026-06-01 | Assigner zephyr




MEDIUM: 6.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H

Problem types

Out-of-bounds Read

Product status

Default status
unaffected

* (git)
affected

References

github.com/...zephyr/security/advisories/GHSA-c3w6-x7m3-3c58

cve.org (CVE-2026-5071)

nvd.nist.gov (CVE-2026-5071)

Download JSON