can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits
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 |
|
|
5.15.545.18.115.19In the Linux kernel, the following vulnerability has been resolved:
can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits
In commit 1be37d3b0414 ("can: m_can: fix periph RX path: use rx-offload to ensure skbs are sent from softirq context") the RX path for peripheral devices was switched to RX-offload.
Received CAN frames are pushed to RX-offload together with a timestamp. RX-offload is designed to handle overflows of the timestamp correctly, if 32 bit timestamps are provided.
The timestamps of m_can core are only 16 bits wide. So this patch shifts them to full 32 bit before passing them to RX-offload.
From the CVE record · Linux
The Linux kernel’s m_can driver passed 16-bit timestamps to RX-offload, which expects 32-bit timestamps to handle overflows correctly. This affects received CAN frames on the peripheral-device RX path; the input does not specify an attacker capability, authentication requirement, or user interaction.
Teams running Linux kernels with the m_can driver on CAN peripheral devices should check their kernel version against the vendor advisory; affected versions are not specified.