diff options
| author | Marc Kleine-Budde <mkl@pengutronix.de> | 2023-06-05 08:27:23 +0200 |
|---|---|---|
| committer | Marc Kleine-Budde <mkl@pengutronix.de> | 2023-06-05 08:27:23 +0200 |
| commit | 628f725d3b090fadcc3735aaf4332e778335188e (patch) | |
| tree | 2dd2fdc8189b5cd3b5b4fb6788f5836de9308dd5 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 2a84aea80e925ecba6349090559754f8e8eb68ef (diff) | |
| parent | 9f16eb106aa5fce15904625661312623ec783ed3 (diff) | |
Merge patch series "can: j1939: avoid possible use-after-free when j1939_can_rx_register fails"
Fedor Pchelkin <pchelkin@ispras.ru> says:
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.
Link: https://lore.kernel.org/r/20230526171910.227615-1-pchelkin@ispras.ru
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions