[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230526171910.227615-1-pchelkin@ispras.ru>
Date: Fri, 26 May 2023 20:19:08 +0300
From: Fedor Pchelkin <pchelkin@...ras.ru>
To: Oleksij Rempel <linux@...pel-privat.de>
Cc: Fedor Pchelkin <pchelkin@...ras.ru>,
Marc Kleine-Budde <mkl@...gutronix.de>,
kernel@...gutronix.de,
Robin van der Gracht <robin@...tonic.nl>,
Oliver Hartkopp <socketcan@...tkopp.net>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Kurt Van Dijck <dev.kurt@...dijck-laurijssen.be>,
linux-can@...r.kernel.org,
netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Alexey Khoroshilov <khoroshilov@...ras.ru>,
lvc-project@...uxtesting.org
Subject: [PATCH 0/2] can: j1939: avoid possible use-after-free when j1939_can_rx_register fails
The patch series fixes a possible racy use-after-free scenario described
in 2/2: if j1939_can_rx_register() fails then the concurrent thread may
have already read the invalid priv structure.
The 1/2 makes j1939_netdev_lock a mutex so that access to
j1939_can_rx_register() can be serialized without changing GFP_KERNEL to
GFP_ATOMIC inside can_rx_register(). This seems to be safe.
Note that the patch series has been tested only via Syzkaller and not with
a real device.
Powered by blists - more mailing lists