From: syzbot <syzbot+d06554f43a8fb48030b0@syzkaller.appspotmail.com>
To: kernel@phwe.de
Cc: kernel@phwe.de, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] [usb?] KASAN: slab-use-after-free Read in skb_dequeue (2)
Date: Tue, 19 May 2026 08:35:34 -0700 [thread overview]
Message-ID: <6a0c8346.170a0220.39a13.0004.GAE@google.com> (raw)
In-Reply-To: <20260519153500.12948-1-kernel@phwe.de>
> #syz test
This crash does not have a reproducer. I cannot test it.
>
> Drain rx_work in btusb_disconnect() before kfree(data) so that any
> work item rescheduled by a late URB completion callback during
> btusb_close() is waited for before the backing data is freed.
>
> ---
> drivers/bluetooth/btusb.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 7f5fce93d984..5d4ea44cd3c9 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -4462,6 +4462,15 @@ static void btusb_disconnect(struct usb_interface *intf)
> usb_driver_release_interface(&btusb_driver, data->intf);
> }
>
> + /*
> + * rx_work is scheduled from URB completion handlers; btusb_close()
> + * (called via hci_unregister_dev) uses a non-sync cancel, so a work
> + * item may still be queued or executing when we reach this point.
> + * Wait for it before freeing data, otherwise the worker dereferences
> + * freed memory through skb_dequeue(&data->acl_q).
> + */
> + cancel_delayed_work_sync(&data->rx_work);
> +
> hci_free_dev(hdev);
> kfree(data);
> }
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-05-19 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 10:47 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in skb_dequeue (2) syzbot
2026-05-19 15:35 ` [syzbot] [bluetooth?] [usb?] " Philipp Weber
2026-05-19 15:35 ` syzbot [this message]
2026-05-19 15:44 ` [RFC PATCH] Bluetooth: btusb: wait for rx_work before freeing data on disconnect Philipp Weber
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=6a0c8346.170a0220.39a13.0004.GAE@google.com \
--to=syzbot+d06554f43a8fb48030b0@syzkaller.appspotmail.com \
--cc=kernel@phwe.de \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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