CVE-2026-80707: can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer
In the Linux kernel, the following vulnerability has been resolved:
can: j1939: transport: j1939sessionfreshnew(): initialize receive buffer
Zero the allocated buffer in j1939sessionfreshnew() 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]
Event History
Frequently Asked Questions
Should the receive-buffer initialization cause a noticeable performance impact?
A performance impact is possible when maximum-sized ETP buffers are allocated. Most real-world use cases are not expected to be noticeably affected, because the maximum known buffer size is typically around 65 KB.
How can I identify the upstream fixes for this issue?
The provided references identify three stable kernel commits: 348818277a3646d5b9fa60c9d20c00dc4bc86832, f3e120a34b336079479fa10f706f0636eaa6e751, and bbfa49d1e287de44994955b44d19281be3195b44.