can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9d71dd0c70099914fcd063135da3c580865e924c · < 8604a3b81b9d0ceaf04fee5f52e701f623a179f9| No fix yet |
| Linux Linux |
|
|
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]
From the CVE record · Linux
The Linux kernel's J1939 transport code does not zero a newly allocated receive buffer, so it may contain residual data. The input does not specify how an attacker could access that data or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with J1939 transport should check their versions; affected versions are not specified.