In 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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade linux | Feb 27, 2025 | Feb 27, 2025 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Feb 26, 2025 |
| Ubuntu | — | Upgrade linux-gkeUpgrade linux-gkeopUpgrade linuxUpgrade linux-riscv-5.15Upgrade linux-gcpUpgrade linux-awsUpgrade linux-oracle-5.15Upgrade linux-hwe-5.15Upgrade linux-realtimeUpgrade linux-azure-fdeUpgrade linux-ibmUpgrade linux-intel-iotg-5.15Upgrade linux-raspiUpgrade linux-lowlatency-hwe-5.15Upgrade linux-oracleUpgrade linux-lowlatencyUpgrade linux-gcp-5.15Upgrade linux-azureUpgrade linux-kvmUpgrade linux-intel-iotgUpgrade linux-aws-5.15Upgrade linux-azure-5.15Upgrade linux-nvidia | Mar 19, 2025 | Feb 26, 2025 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub