From: patchwork-bot+bluetooth@kernel.org
To: Raphael Pinsonneault-Thibeault <rpthibeault@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
syzbot+2fc81b50a4f8263a159b@syzkaller.appspotmail.com,
skhan@linuxfoundation.org
Subject: Re: [PATCH] Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF
Date: Fri, 07 Nov 2025 19:10:12 +0000 [thread overview]
Message-ID: <176254261224.1132280.14674857749168928355.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251105192839.895418-3-rpthibeault@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 5 Nov 2025 14:28:41 -0500 you wrote:
> There is a KASAN: slab-use-after-free read in btusb_disconnect().
> Calling "usb_driver_release_interface(&btusb_driver, data->intf)" will
> free the btusb data associated with the interface. The same data is
> then used later in the function, hence the UAF.
>
> Fix by moving the accesses to btusb data to before the data is free'd.
>
> [...]
Here is the summary with links:
- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF
https://git.kernel.org/bluetooth/bluetooth-next/c/162d88a68ccb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-07 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 19:28 [PATCH] Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF Raphael Pinsonneault-Thibeault
2025-11-07 19:10 ` patchwork-bot+bluetooth [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=176254261224.1132280.14674857749168928355.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=rpthibeault@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+2fc81b50a4f8263a159b@syzkaller.appspotmail.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