linux-cve-announce - CVE-2022-49659: can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025022622-CVE-2022-49659-31c4@gregkh>
Date: Wed, 26 Feb 2025 03:23:42 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49659: can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits

Description
===========

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.

The Linux kernel CVE team has assigned CVE-2022-49659 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.13 with commit 1be37d3b0414e3db47f6fcba6c16286bbae0cb65 and fixed in 5.15.54 with commit c7333f79888497bfd75dcd02a94eaf836dd1042c
	Issue introduced in 5.13 with commit 1be37d3b0414e3db47f6fcba6c16286bbae0cb65 and fixed in 5.18.11 with commit 2a2914a5bd7f38efe55a8372178146de82e0bce9
	Issue introduced in 5.13 with commit 1be37d3b0414e3db47f6fcba6c16286bbae0cb65 and fixed in 5.19 with commit 4c3333693f07313f5f0145a922f14a7d3c0f4f21

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-49659
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/net/can/m_can/m_can.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/c7333f79888497bfd75dcd02a94eaf836dd1042c
	https://git.kernel.org/stable/c/2a2914a5bd7f38efe55a8372178146de82e0bce9
	https://git.kernel.org/stable/c/4c3333693f07313f5f0145a922f14a7d3c0f4f21