Stack Buffer Overflow in Open-SAE-J1939 SAE_J1939_Read_Binary_Data_Transfer_DM16
CVE-2026-42467 is a stack buffer overflow in Open-SAE-J1939 affecting versions through commit b6caf884df46435e539b1ecbf92b6c29b345bdfe (2025-11-30). The flaw is in SAE_J1939_Read_Binary_Data_Transfer_DM16 while parsing malformed J1939 traffic. According to the provided context, a crafted CAN frame on the J1939 bus can trigger unsafe handling during message parsing, resulting in a stack-based overwrite. The issue is described as independent from the related Open-SAE-J1939 size/overhead arithmetic bug tracked separately as CVE-2026-37534.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can cause denial of service by crashing the affected process or device handling J1939 traffic. Because the vulnerability is a stack buffer overflow triggered by attacker-controlled frame content, memory corruption occurs on the stack and could potentially have consequences beyond a crash depending on compiler, platform, memory protections, and surrounding code; however, the provided content specifically confirms denial of service.
If you can’t patch tonight, do this now.
Until a fixed release is deployed, restrict exposure of systems using Open-SAE-J1939 to untrusted CAN/J1939 traffic. Filter or gate malformed or unexpected DM16/Binary Data Transfer messages at CAN gateways, isolate diagnostic and research networks from untrusted bus participants, and monitor for crashes or anomalous J1939 traffic patterns. Where feasible, harden builds with stack protections and memory-safety defenses, though these measures do not remove the underlying flaw.
Patch, then assume compromise.
Upgrade Open-SAE-J1939 to a version containing a fix after commit b6caf884df46435e539b1ecbf92b6c29b345bdfe, once available. Review and correct bounds checking in SAE_J1939_Read_Binary_Data_Transfer_DM16 so that all attacker-influenced lengths derived from J1939/CAN frames are validated before copying or reassembly into stack buffers. Add explicit upper-bound checks, reject malformed DM16/Binary Data Transfer frames, and use safer memory-handling patterns that enforce destination buffer size.
No public exploits tracked yet. Mallory keeps watching.
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.