KernelScan.io

HIGH Introduced in 5.4

j1939 ReceiveBuffer Leak

CVE-2026-80707

CVSS 7.5 / 10.0 NVD

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

KernelScan AI3.3LOW

01

In the Linux kernel, the following vulnerability has been resolved: can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer Zero the allocated buffer in j1939_session_fresh_new() to ensure it contains no residual data. While there is a potential performance impact if users allocate maximum sized ETP buffers, most real-world use cases are not noticeably affected since the maximum known buffer size is typically around 65K. [mkl: add Message-ID]

02

Engine v0.6.0

Risk summary

The J1939 CAN transport layer allocates a receive buffer without zeroing it, allowing stale kernel heap data to leak to userspace when the buffer is read. Any user who can open a J1939 socket — which requires CAP_NET_ADMIN, obtainable via user namespaces on unhardened systems — can trigger this. The leaked data may contain sensitive kernel information from prior allocations.

Affectednet/can/j1939/transport.c (can: j1939)

Vulnerability analysis

The J1939 transport layer allocates a receive buffer for incoming session data but does not initialize it, so the buffer may contain residual data from previous kernel slab allocations. When userspace reads from this buffer, the uninitialized portions can expose whatever data was left in that memory, potentially including kernel pointers or other sensitive information. The fix replaces the plain buffer allocation with a zeroing variant so the entire receive buffer is cleared before any data is written into it. This can be triggered by any user who can create a J1939 socket over a CAN interface, which requires CAP_NET_ADMIN — a capability an unprivileged user can obtain through user namespaces on systems where they are enabled.

03

BranchIntroducedFixed inPatch commit
5.105.45.10.265348818277a36
5.155.45.15.216f3e120a34b33
6.15.46.1.183bbfa49d1e287
6.125.46.12.103038bad8e16c2
6.185.46.18.448604a3b81b9d
6.65.46.6.151194d67e92197
7.15.47.1.8d5b3613c7d69
mainline5.47.2eb96c5890792
cip/5.105.45.10.268-cip77348818277a36
cip/5.10-rt5.45.10.268-cip77-rt34348818277a36
cip/6.15.46.1.187-cip60bbfa49d1e287
cip/6.1-rt5.46.1.189-cip61-rt32bbfa49d1e287
cip/6.125.46.12.104-cip30038bad8e16c2

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.104-cip30
cip/6.1Fixed in 6.1.187-cip60
cip/6.1-rtFixed in 6.1.189-cip61-rt32
cip/5.10Fixed in 5.10.268-cip77
cip/5.10-rtFixed in 5.10.268-cip77-rt34