Oliver Hartkopp 6d7d458c41 can: bcm: add missing rcu read protection for procfs content ... commit dac5e62491 upstream. When the procfs content is generated for a bcm_op which is in the process to be removed the procfs output might show unreliable data (UAF). As the removal of bcm_op's is already implemented with rcu handling this patch adds the missing rcu_read_lock() and makes sure the list entries are properly removed under rcu protection. Fixes: f1b4e32aca ("can: bcm: use call_rcu() instead of costly synchronize_rcu()") Reported-by: Anderson Nascimento <anderson@allelesecurity.com> Suggested-by: Anderson Nascimento <anderson@allelesecurity.com> Tested-by: Anderson Nascimento <anderson@allelesecurity.com> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Link: https://patch.msgid.link/20250519125027.11900-2-socketcan@hartkopp.net Cc: stable@vger.kernel.org # >= 5.4 Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2025-06-04 14:40:20 +02:00
..
j1939	can: j1939: j1939_sk_send_loop(): fix unable to send messages with data length zero	2025-02-21 13:50:04 +01:00
af_can.c	can: statistics: use atomic access in hot path	2025-04-10 14:33:39 +02:00
af_can.h	can: statistics: use atomic access in hot path	2025-04-10 14:33:39 +02:00
bcm.c	can: bcm: add missing rcu read protection for procfs content	2025-06-04 14:40:20 +02:00
gw.c	can: gw: fix RCU/BH usage in cgw_create_job()	2025-05-18 08:21:21 +02:00
isotp.c
Kconfig
Makefile
proc.c	can: statistics: use atomic access in hot path	2025-04-10 14:33:39 +02:00
raw.c	can: raw: add support for SO_MARK	2024-01-10 17:10:23 +01:00