CVE-2022-49659
- Source
- https://cve.org/CVERecord?id=CVE-2022-49659
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-49659.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2022-49659
- Downstream
- Published
- 2025-02-26T02:23:57.411Z
- Modified
- 2026-05-15T11:54:13.394153961Z
- Summary
- can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
can: mcan: mcan_{readfifo,echotx_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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49659.json", "cna_assigner": "Linux" }- References
-
- https://git.kernel.org/stable/c/2a2914a5bd7f38efe55a8372178146de82e0bce9
- https://git.kernel.org/stable/c/4c3333693f07313f5f0145a922f14a7d3c0f4f21
- https://git.kernel.org/stable/c/c7333f79888497bfd75dcd02a94eaf836dd1042c
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49659.json
- https://nvd.nist.gov/vuln/detail/CVE-2022-49659
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git