[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168859802462.24898.5386569963493900697.git-patchwork-notify@kernel.org>
Date: Wed, 05 Jul 2023 23:00:24 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Doug Anderson <dianders@...omium.org>
Cc: marcel@...tmann.org, johan.hedberg@...il.com, luiz.dentz@...il.com,
swboyd@...omium.org, mmandlik@...gle.com, mcchou@...gle.com,
linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/2] Bluetooth: hci_sync: Avoid use-after-free in dbg for
hci_remove_adv_monitor()
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:
On Fri, 30 Jun 2023 15:33:14 -0700 you wrote:
> KASAN reports that there's a use-after-free in
> hci_remove_adv_monitor(). Trawling through the disassembly, you can
> see that the complaint is from the access in bt_dev_dbg() under the
> HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because
> msft_remove_monitor() can end up freeing the monitor
> structure. Specifically:
> hci_remove_adv_monitor() ->
> msft_remove_monitor() ->
> msft_remove_monitor_sync() ->
> msft_le_cancel_monitor_advertisement_cb() ->
> hci_free_adv_monitor()
>
> [...]
Here is the summary with links:
- [v3,1/2] Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()
https://git.kernel.org/bluetooth/bluetooth-next/c/2648c5eb33ca
- [v3,2/2] Bluetooth: hci_sync: Don't double print name in add/remove adv_monitor
https://git.kernel.org/bluetooth/bluetooth-next/c/22d2055a576d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists