cve/published/2023/CVE-2023-52887.mbox

From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2023-52887: net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new

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

In the Linux kernel, the following vulnerability has been resolved:

net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new

This patch enhances error handling in scenarios with RTS (Request to
Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE
backtraces with a new error handling method. This provides clearer error
messages and allows for the early termination of problematic sessions.
Previously, sessions were only released at the end of j1939_xtp_rx_rts().

Potentially this could be reproduced with something like:
testj1939 -r vcan0:0x80 &
while true; do
	# send first RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send second RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send abort
	cansend vcan0 18EC8090#ff00000000002301;
done

The Linux kernel CVE team has assigned CVE-2023-52887 to this issue.


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

	Issue introduced in 5.4 with commit 9d71dd0c70099914fcd063135da3c580865e924c and fixed in 5.4.279 with commit ed581989d7ea9df6f8646beba2341e32cd49a1f9
	Issue introduced in 5.4 with commit 9d71dd0c70099914fcd063135da3c580865e924c and fixed in 5.10.221 with commit f6c839e717901dbd6b1c1ca807b6210222eb70f6
	Issue introduced in 5.4 with commit 9d71dd0c70099914fcd063135da3c580865e924c and fixed in 5.15.162 with commit 1762ca80c2b72dd1b5821c5e347713ae696276ea
	Issue introduced in 5.4 with commit 9d71dd0c70099914fcd063135da3c580865e924c and fixed in 6.1.97 with commit 26b18dd30e63d4fd777be429148e8e4ed66f60b2
	Issue introduced in 5.4 with commit 9d71dd0c70099914fcd063135da3c580865e924c and fixed in 6.6.37 with commit 177e33b655d35d72866b50aec84307119dc5f3d4
	Issue introduced in 5.4 with commit 9d71dd0c70099914fcd063135da3c580865e924c and fixed in 6.9.8 with commit 0bc0a7416ea73f79f915c9a05ac0858dff65cfed
	Issue introduced in 5.4 with commit 9d71dd0c70099914fcd063135da3c580865e924c and fixed in 6.10 with commit d3e2904f71ea0fe7eaff1d68a2b0363c888ea0fb

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-2023-52887
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:
	net/can/j1939/transport.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/ed581989d7ea9df6f8646beba2341e32cd49a1f9
	https://git.kernel.org/stable/c/f6c839e717901dbd6b1c1ca807b6210222eb70f6
	https://git.kernel.org/stable/c/1762ca80c2b72dd1b5821c5e347713ae696276ea
	https://git.kernel.org/stable/c/26b18dd30e63d4fd777be429148e8e4ed66f60b2
	https://git.kernel.org/stable/c/177e33b655d35d72866b50aec84307119dc5f3d4
	https://git.kernel.org/stable/c/0bc0a7416ea73f79f915c9a05ac0858dff65cfed
	https://git.kernel.org/stable/c/d3e2904f71ea0fe7eaff1d68a2b0363c888ea0fb