From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, tristan@talencesecurity.com,
linux-mediatek@lists.infradead.org, sean.wang@mediatek.com,
mark-yw.chen@mediatek.com
Subject: Re: [PATCH] Bluetooth: btmtk: accept too short WMT FUNC_CTRL events
Date: Mon, 11 May 2026 14:30:04 +0000 [thread overview]
Message-ID: <177850980405.2266296.3114753928820395948.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <770d36b07311bf88210c187923f243fb9f126f04.1777058551.git.pav@iki.fi>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 24 Apr 2026 22:24:29 +0300 you wrote:
> MT7925 (USB ID 0e8d:e025) on fw version 20260106153314 sends WMT
> FUNC_CTRL events that are missing the status field.
>
> Prior to commit 006b9943b982 ("Bluetooth: btmtk: validate WMT event SKB
> length before struct access") the status was read from out-of-bounds of
> SKB data, which usually would result to success with
> BTMTK_WMT_ON_UNDONE, although I don't know the intent here. The bounds
> check added in that commit returns with error instead, producing
> "Bluetooth: hci0: Failed to send wmt func ctrl (-22)" and makes the
> device unusable.
>
> [...]
Here is the summary with links:
- Bluetooth: btmtk: accept too short WMT FUNC_CTRL events
https://git.kernel.org/bluetooth/bluetooth-next/c/162b1adeb057
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:[~2026-05-11 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 19:24 [PATCH] Bluetooth: btmtk: accept too short WMT FUNC_CTRL events Pauli Virtanen
2026-04-24 19:38 ` Luiz Augusto von Dentz
2026-05-08 19:09 ` Pauli Virtanen
2026-05-08 19:19 ` Mikhail Gavrilov
2026-05-11 14:46 ` Luiz Augusto von Dentz
2026-04-24 19:59 ` bluez.test.bot
2026-05-11 14:30 ` 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=177850980405.2266296.3114753928820395948.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mark-yw.chen@mediatek.com \
--cc=pav@iki.fi \
--cc=sean.wang@mediatek.com \
--cc=tristan@talencesecurity.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