Bug 2347817 (CVE-2022-49659) - CVE-2022-49659 kernel: can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits
Summary: CVE-2022-49659 kernel: can: m_can: m_can_{read_fifo,echo_tx_event}(): shift t...
Keywords:
Status: NEW
Alias: CVE-2022-49659
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-26 03:07 UTC by OSIDB Bzimport
Modified: 2025-02-27 09:22 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-26 03:07:47 UTC
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.

Comment 1 Avinash Hanwate 2025-02-26 12:21:30 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022622-CVE-2022-49659-31c4@gregkh/T

Comment 4 Avinash Hanwate 2025-02-26 16:27:08 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022622-CVE-2022-49659-31c4@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.