net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9d71dd0c70099914fcd063135da3c580865e924c · < 6121b7564c725b632ffe4764abe85aa239d37703| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts
Since j1939_session_deactivate_activate_next() in j1939_tp_rxtimer() is called only when the timer is enabled, we need to call j1939_session_deactivate_activate_next() if we cancelled the timer. Otherwise, refcount for j1939_session leaks, which will later appear as
| unregister_netdevice: waiting for vcan0 to become free. Usage count = 2.
problem.
From the CVE record · Linux
The Linux kernel CAN J1939 code can leak a session reference when it receives a second RTS and cancels the session timer without deactivating the session. This can leave a network device waiting to become free during unregister; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with CAN J1939 support should check their exposure; affected versions are not specified.