[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<176366460701.1748676.511972373877694762.git-patchwork-notify@kernel.org>
Date: Thu, 20 Nov 2025 18:50:07 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Doug Anderson <dianders@...omium.org>
Cc: marcel@...tmann.org, luiz.dentz@...il.com, matthias.bgg@...il.com,
angelogioacchino.delregno@...labora.com, regressions@...mhuis.info,
regressions@...ts.linux.dev, incogcyberpunk@...ton.me,
johan.hedberg@...il.com, sean.wang@...iatek.com, stable@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-bluetooth@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v3] Bluetooth: btusb: mediatek: Avoid
btusb_mtk_claim_iso_intf() NULL deref
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:
On Thu, 20 Nov 2025 08:12:28 -0800 you wrote:
> In btusb_mtk_setup(), we set `btmtk_data->isopkt_intf` to:
> usb_ifnum_to_if(data->udev, MTK_ISO_IFNUM)
>
> That function can return NULL in some cases. Even when it returns
> NULL, though, we still go on to call btusb_mtk_claim_iso_intf().
>
> As of commit e9087e828827 ("Bluetooth: btusb: mediatek: Add locks for
> usb_driver_claim_interface()"), calling btusb_mtk_claim_iso_intf()
> when `btmtk_data->isopkt_intf` is NULL will cause a crash because
> we'll end up passing a bad pointer to device_lock(). Prior to that
> commit we'd pass the NULL pointer directly to
> usb_driver_claim_interface() which would detect it and return an
> error, which was handled.
>
> [...]
Here is the summary with links:
- [v3] Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref
https://git.kernel.org/bluetooth/bluetooth-next/c/dd6dda907d09
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