CVE-2026-5071: Out-of-bounds Read in zephyrproject-rtos Zephyr
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.
AI Analysis
Technical Summary
The vulnerability exists in Zephyr's SocketCAN implementation where the function zcan_sendto_ctx() uses a NET_ASSERT to validate the length of a user-supplied socketcan_frame buffer before it is dereferenced in socketcan_to_can_frame(). Since assertions are disabled in production builds, an attacker controlling the length parameter to the sendto syscall can provide a truncated frame. This results in socketcan_to_can_frame() reading beyond the buffer boundary, causing an out-of-bounds read. The impact includes potential denial-of-service due to crashes and information leakage of adjacent memory via transmitted frame contents.
Potential Impact
This vulnerability can lead to denial-of-service conditions by crashing the system due to out-of-bounds memory reads. Additionally, because the parsed frame contents are transmitted on the network, there is a risk of leaking adjacent memory contents, which may expose sensitive information. The CVSS score of 6.1 reflects a medium severity with local attack vector, low attack complexity, and limited confidentiality impact but high availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should exercise caution when handling untrusted userspace inputs to the SocketCAN interface. Consider disabling or restricting access to the affected SocketCAN functionality if possible to reduce risk.
CVE-2026-5071: Out-of-bounds Read in zephyrproject-rtos Zephyr
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.
CVSS v3.1
Score 6.1medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in Zephyr's SocketCAN implementation where the function zcan_sendto_ctx() uses a NET_ASSERT to validate the length of a user-supplied socketcan_frame buffer before it is dereferenced in socketcan_to_can_frame(). Since assertions are disabled in production builds, an attacker controlling the length parameter to the sendto syscall can provide a truncated frame. This results in socketcan_to_can_frame() reading beyond the buffer boundary, causing an out-of-bounds read. The impact includes potential denial-of-service due to crashes and information leakage of adjacent memory via transmitted frame contents.
Potential Impact
This vulnerability can lead to denial-of-service conditions by crashing the system due to out-of-bounds memory reads. Additionally, because the parsed frame contents are transmitted on the network, there is a risk of leaking adjacent memory contents, which may expose sensitive information. The CVSS score of 6.1 reflects a medium severity with local attack vector, low attack complexity, and limited confidentiality impact but high availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should exercise caution when handling untrusted userspace inputs to the SocketCAN interface. Consider disabling or restricting access to the affected SocketCAN functionality if possible to reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- zephyr
- Date Reserved
- 2026-03-27T23:41:28.910Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1a99e5e29bf47b50fb7f2a
Added to database: 05/30/2026, 08:03:49 UTC
Last enriched: 06/06/2026, 21:01:10 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 90
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.