can: isotp: split tx timer into transmission and timeout
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.1.116.2In the Linux kernel, the following vulnerability has been resolved:
can: isotp: split tx timer into transmission and timeout
The timer for the transmission of isotp PDUs formerly had two functions: 1. send two consecutive frames with a given time gap 2. monitor the timeouts for flow control frames and the echo frames
This led to larger txstate checks and potentially to a problem discovered by syzbot which enabled the panic_on_warn feature while testing.
The former 'txtimer' function is split into 'txfrtimer' and 'txtimer' to handle the two above functionalities with separate timer callbacks.
The two simplified timers now run in one-shot mode and make the state transitions (especially with isotp_rcv_echo) better understandable.
From the CVE record · Linux
The Linux kernel CAN ISO-TP transmission timer handled both frame spacing and timeout monitoring, leading to a problem found during testing. A warning could cause a kernel panic when panic_on_warn is enabled; the input does not specify attacker access, authentication, or user-interaction requirements.
Engineers running Linux kernels with CAN ISO-TP support should check their kernel versions; affected versions are not specified.