From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Sam P <sam@bynar.io>, netdev@vger.kernel.org
Cc: mkl@pengutronix.de, linux-kernel@vger.kernel.org,
linux-can@vger.kernel.org
Subject: Re: [PATCH net] can: raw: fix ro->uniq use-after-free in raw_rcv()
Date: Wed, 8 Apr 2026 21:32:20 +0200 [thread overview]
Message-ID: <4fe2b2fd-e3f3-445f-9e06-411bfd9dd906@hartkopp.net> (raw)
In-Reply-To: <26ec626d-cae7-4418-9782-7198864d070c@bynar.io>
On 08.04.26 16:30, Sam P wrote:
> raw_release() unregisters raw CAN receive filters via can_rx_unregister(),
> but receiver deletion is deferred with call_rcu(). This leaves a window
> where raw_rcv() may still be running in an RCU read-side critical section
> after raw_release() frees ro->uniq, leading to a use-after-free of the
> percpu uniq storage.
>
> Move free_percpu(ro->uniq) out of raw_release() and into a raw-specific
> socket destructor. can_rx_unregister() takes an extra reference to the
> socket and only drops it from the RCU callback, so freeing uniq from
> sk_destruct ensures the percpu area is not released until the relevant
> callbacks have drained.
>
> Fixes: 514ac99c64b2 ("can: fix multiple delivery of a single CAN frame
> for overlapping CAN filters")
> Cc: stable@vger.kernel.org # v4.1+
> Assisted-by: Bynario AI
> Signed-off-by: Samuel Page <sam@bynar.io>
Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
>
> ---
> net/can/raw.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/net/can/raw.c b/net/can/raw.c
> index eee244ffc31e..f042c4316890 100644
> --- a/net/can/raw.c
> +++ b/net/can/raw.c
> @@ -361,6 +361,14 @@ static int raw_notifier(struct notifier_block *nb,
> unsigned long msg,
> return NOTIFY_DONE;
> }
>
> +static void raw_sock_destruct(struct sock *sk)
> +{
> + struct raw_sock *ro = raw_sk(sk);
> +
> + free_percpu(ro->uniq);
> + can_sock_destruct(sk);
> +}
> +
> static int raw_init(struct sock *sk)
> {
> struct raw_sock *ro = raw_sk(sk);
> @@ -387,6 +395,8 @@ static int raw_init(struct sock *sk)
> if (unlikely(!ro->uniq))
> return -ENOMEM;
>
> + sk->sk_destruct = raw_sock_destruct;
> +
> /* set notifier */
> spin_lock(&raw_notifier_lock);
> list_add_tail(&ro->notifier, &raw_notifier_list);
> @@ -436,7 +446,6 @@ static int raw_release(struct socket *sock)
> ro->bound = 0;
> ro->dev = NULL;
> ro->count = 0;
> - free_percpu(ro->uniq);
>
> sock_orphan(sk);
> sock->sk = NULL;
prev parent reply other threads:[~2026-04-08 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 14:30 [PATCH net] can: raw: fix ro->uniq use-after-free in raw_rcv() Sam P
2026-04-08 16:28 ` Oliver Hartkopp
2026-04-08 17:22 ` Sam P
2026-04-08 19:31 ` Oliver Hartkopp
2026-04-08 19:32 ` Oliver Hartkopp [this message]
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=4fe2b2fd-e3f3-445f-9e06-411bfd9dd906@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=sam@bynar.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox