From: Pauli Virtanen <pav@iki.fi>
To: ssrane_b23@ee.vjti.ac.in
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
david.hunter.linux@gmail.com, khalid@kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user
Date: Wed, 05 Nov 2025 21:36:23 +0200 [thread overview]
Message-ID: <e795d2b600d98bfaf9b63088929e8ac0e8d4e3ba.camel@iki.fi> (raw)
In-Reply-To: <20251105142251.101852-1-ssranevjti@gmail.com>
ke, 2025-11-05 kello 19:52 +0530, ssrane_b23@ee.vjti.ac.in kirjoitti:
> From: Shaurya Rane <ssrane_b23@ee.vjti.ac.in>
>
> Syzbot reported a use-after-free in l2cap_unregister_user(), caused by
> missing reference counting on the associated hci_dev. If the device is
> unregistered while L2CAP users are still active, l2cap_unregister_user()
> may access a freed hci_dev when taking its lock.
>
> Fix this by taking a device reference in l2cap_register_user() using
> hci_dev_hold(), and releasing it in l2cap_unregister_user() via
> hci_dev_put(). This ensures the hci_dev remains valid for the lifetime
> of registered L2CAP users.
>
> Reported-by: syzbot+14b6d57fb728e27ce23c@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=14b6d57fb728e27ce23c
> Fixes: c8992cffbe74 ("Bluetooth: hci_event: Use of a function table to handle Command Complete")
> Signed-off-by: Shaurya Rane <ssrane_b23@ee.vjti.ac.in>
> ---
> net/bluetooth/l2cap_core.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index 805c752ac0a9..6a880f8ab6c2 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -1688,6 +1688,11 @@ int l2cap_register_user(struct l2cap_conn *conn, struct l2cap_user *user)
> struct hci_dev *hdev = conn->hcon->hdev;
> int ret;
>
> + /* Hold a reference to hdev to prevent it from being freed while
> + * we have registered users.
> + */
> + hci_dev_hold(hdev);
> +
> /* We need to check whether l2cap_conn is registered. If it is not, we
> * must not register the l2cap_user. l2cap_conn_del() is unregisters
> * l2cap_conn objects, but doesn't provide its own locking. Instead, it
The old comment here seems out of date since commit ab4eedb790cae,
currently l2cap_conn_del() appears to be using conn->lock to do
mutex_lock(&conn->lock);
...
l2cap_unregister_all_users(conn);
...
hci_chan_del(conn->hchan);
conn->hchan = NULL;
...
mutex_unlock(&conn->lock);
so it looks likely also taking conn->lock could avoid the races with
conn->users and conn->hchan.
> @@ -1717,6 +1722,10 @@ int l2cap_register_user(struct l2cap_conn *conn, struct l2cap_user *user)
>
> out_unlock:
> hci_dev_unlock(hdev);
> +
> + if (ret)
> + hci_dev_put(hdev);
> +
> return ret;
> }
> EXPORT_SYMBOL(l2cap_register_user);
> @@ -1735,6 +1744,9 @@ void l2cap_unregister_user(struct l2cap_conn *conn, struct l2cap_user *user)
>
> out_unlock:
> hci_dev_unlock(hdev);
> +
> + /* Release the reference we took in l2cap_register_user */
> + hci_dev_put(hdev);
> }
> EXPORT_SYMBOL(l2cap_unregister_user);
>
--
Pauli Virtanen
next prev parent reply other threads:[~2025-11-05 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 14:22 [PATCH] Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user ssrane_b23
2025-11-05 19:36 ` Pauli Virtanen [this message]
2025-11-06 18:20 ` [PATCH v2 1/1] " ssrane_b23
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=e795d2b600d98bfaf9b63088929e8ac0e8d4e3ba.camel@iki.fi \
--to=pav@iki.fi \
--cc=david.hunter.linux@gmail.com \
--cc=khalid@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=ssrane_b23@ee.vjti.ac.in \
/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