From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org
Cc: Oliver Hartkopp <socketcan@hartkopp.net>
Subject: [PATCH v8 0/7] can: protect the receive lists with a per-device lock
Date: Fri, 23 Oct 2026 14:17:54 +0200 [thread overview]
Message-ID: <20261023121801.3052075-1-socketcan@hartkopp.net> (raw)
This series fixes a use-after-free in CAN_ISOTP and CAN_BCM that can be
triggered when a CAN device is moved to another network namespace while
a socket bound to this device is released [1].
Patch 5 makes isotp_bind() check the return values of can_rx_register(),
so that bind() does not succeed with missing receivers.
Patch 7 copies the CAN_RAW and CAN_ISOTP specific socket options from
and to user space outside of lock_sock(), so that a stalled copy can not
block raw_notify() waiting for lock_sock() under RTNL.
The code of patches 1-4 is unchanged. Only the commit message of patch 4
has been updated after the Sashiko review of v4 to describe the actual
NULL pointer dereference in can_rx_unregister() and the CAN_ISOTP path
that reaches it.
The series is based on linux-can-next/testing, which also contains
"can: raw: remove redundant NULL check before netdev_hold()" from [2].
The idea behind patch 6:
The receive lists of a CAN device are located in the device's
can_ml_priv and travel with the device when it is moved to another
network namespace. But they are protected by the per-netns
rcvlists_lock, so the lock that protects a device's lists depends on
the namespace the caller passes to can_rx_register() and
can_rx_unregister(). can_rx_unregister() silently returns when this
namespace does not match dev_net(dev) anymore.
isotp_release() and bcm_release() leave the netdev notifier list before
they can serialize against the notifier. When the device changes its
namespace in this window, their filters are not removed and the
remaining receivers point to the freed socket or bcm op.
Taking RTNL in these release paths is no option, as CAN_RAW already
holds RTNL while adding and removing up to CAN_RAW_FILTER_MAX filters
per socket, which unprivileged users can trigger repeatedly.
Instead, patch 6 protects the receive lists where they are located: A
spinlock in struct can_dev_rcv_lists protects the lists of a CAN device
(initialized in can_set_ml_priv()) or the 'any' CAN device lists of a
namespace (initialized in can_pernet_init()). can_rx_unregister() then
finds the subscription independently of the current namespace of the
device, which is kept accessible by the tracked device references the
protocols already hold. The per-netns rcvlists_lock only protects the
receive list statistics, for which CAN_RAW, CAN_BCM and CAN_ISOTP pass
the namespace that has been used for can_rx_register().
As a consequence, CAN_RAW and CAN_ISOTP do not need RTNL in bind(),
setsockopt() and release() anymore. bind() is serialized against
NETDEV_UNREGISTER by publishing the device inside the RCU section of
its lookup, as unlist_netdevice() and synchronize_net() precede
NETDEV_UNREGISTER both on unregistration and on a namespace change.
The notifiers recheck the binding under lock_sock(). As RTNL does not
keep NETDEV_DOWN out of bind() anymore, bind() checks IFF_UP after
publishing the bound device, with an smp_mb() pair against the
notifiers, so a down transition during bind() is still reported with
ENETDOWN.
Changes in v8:
- new patch 5: check the return values of can_rx_register() in
isotp_bind() (Sashiko review)
- patch 6 rebased on patch 5: isotp_bind() resets the published so->dev
again when the registration of a receiver fails and checks IFF_UP at
the end of a successful bind(), as raw_bind() does
- patch 6: isotp_notify() reports NETDEV_DOWN only for a bound socket, so
a failing isotp_bind() can not get a needless ENETDOWN
- patch 6: isotp_sendmsg() and isotp_recvmsg() read so->bound with
READ_ONCE()
- patch 6: moved copying the user space data outside of lock_sock() in
raw_setsockopt() to patch 7 to keep patch 6 focused on the locking
changes and to ease review
- new patch 7: copy the CAN_RAW and CAN_ISOTP socket options outside of
lock_sock() (Sashiko review)
Changes in v7 (details in patch 6):
- report ENETDOWN in bind() and ENODEV for NETDEV_UNREGISTER under
lock_sock(), so ENODEV can not be overwritten by ENETDOWN (Sashiko
review)
Changes in v6:
- isotp_bind() checks the device before publishing so->dev, so a
failing bind() can not get a needless ENETDOWN (Sashiko review)
Changes in v5:
- report ENETDOWN for a down transition during bind() again (Sashiko
review)
- comment and kernel-doc updates (Sashiko review)
- patch 4: commit message describes the actual crash path (Sashiko
review)
[1] https://lore.kernel.org/linux-can/CEA6A38A-2646-4ADA-95B4-CBAE2F301A8E@doyensec.com/
[2] https://lore.kernel.org/linux-can/20261018164417.1540449-1-mkl@pengutronix.de/
Previous versions of patch 6:
v7: https://lore.kernel.org/linux-can/20261022114202.180023-6-socketcan@hartkopp.net/
v6: https://lore.kernel.org/linux-can/20261021231130.2085690-12-mkl@pengutronix.de/
v5: https://lore.kernel.org/linux-can/20261020203257.230955-6-socketcan@hartkopp.net/
v4: https://lore.kernel.org/linux-can/20261019152741.54854-6-socketcan@hartkopp.net/
v3: https://lore.kernel.org/linux-can/20261019074244.50391-5-socketcan@hartkopp.net/
v2: https://lore.kernel.org/linux-can/20261018180739.689750-1-socketcan@hartkopp.net/
v1: https://lore.kernel.org/linux-can/20261017201935.399233-1-socketcan@hartkopp.net/
Oliver Hartkopp (6):
can: proc: skip stats calculation after reset in can_stat_update()
can: proc: remove pointers from CAN specific proc output
can: replace ARPHRD_CAN type checks with can_get_ml_priv()
can: isotp: check the return values of can_rx_register() in
isotp_bind()
can: protect the receive lists with a per-device lock
can: raw, isotp: copy socket options outside of lock_sock()
Runyu Xiao (1):
can: proc: reset pkg_stats atomics individually
Documentation/networking/can.rst | 16 +-
include/linux/can/can-ml.h | 3 +
include/linux/can/core.h | 2 +-
include/net/netns/can.h | 2 +-
net/can/af_can.c | 60 ++++---
net/can/af_can.h | 2 +-
net/can/bcm.c | 64 +++----
net/can/gw.c | 9 +-
net/can/isotp.c | 206 ++++++++++++++---------
net/can/j1939/main.c | 2 +-
net/can/proc.c | 95 ++++++-----
net/can/raw.c | 278 ++++++++++++++++++-------------
12 files changed, 427 insertions(+), 312 deletions(-)
--
2.43.0
next reply other threads:[~2026-10-23 12:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 12:17 Oliver Hartkopp [this message]
2026-10-23 12:17 ` [PATCH v8 1/7] can: proc: reset pkg_stats atomics individually Oliver Hartkopp
2026-10-23 12:17 ` [PATCH v8 2/7] can: proc: skip stats calculation after reset in can_stat_update() Oliver Hartkopp
2026-10-23 12:17 ` [PATCH v8 3/7] can: proc: remove pointers from CAN specific proc output Oliver Hartkopp
2026-10-23 12:17 ` [PATCH v8 4/7] can: replace ARPHRD_CAN type checks with can_get_ml_priv() Oliver Hartkopp
2026-10-23 12:17 ` [PATCH v8 5/7] can: isotp: check the return values of can_rx_register() in isotp_bind() Oliver Hartkopp
2026-10-23 12:18 ` [PATCH v8 6/7] can: protect the receive lists with a per-device lock Oliver Hartkopp
2026-10-23 12:18 ` [PATCH v8 7/7] can: raw, isotp: copy socket options outside of lock_sock() Oliver Hartkopp
2026-10-25 11:28 ` [PATCH v8 0/7] can: protect the receive lists with a per-device lock Marc Kleine-Budde
2026-10-25 18:55 ` Oliver Hartkopp
2026-10-25 19:06 ` Marc Kleine-Budde
2026-10-25 19:16 ` Oliver Hartkopp
2026-10-25 19:19 ` Marc Kleine-Budde
2026-10-25 19:22 ` Oliver Hartkopp
2026-10-25 19:43 ` Marc Kleine-Budde
2026-10-25 19:51 ` Oliver Hartkopp
2026-10-25 20:01 ` Marc Kleine-Budde
2026-10-25 20:02 ` Marc Kleine-Budde
2026-10-25 11:43 ` Oliver Hartkopp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261023121801.3052075-1-socketcan@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.