From: patchwork-bot+bluetooth@kernel.org
To: Chris Lu <chris.lu@mediatek.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, sean.wang@mediatek.com,
will-cy.Lee@mediatek.com, ss.wu@mediatek.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 0/2] Bluetooth: btmtksdio: Fix SKB handling in the TX path
Date: Mon, 17 Aug 2026 19:45:57 +0000 [thread overview]
Message-ID: <178699595738.1691257.9499694982738760170.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260817095332.182994-1-chris.lu@mediatek.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 17 Aug 2026 17:53:30 +0800 you wrote:
> btmtksdio_tx_packet() rounds the SDIO transfer size up to the 256 byte
> block size, but never grows the SKB accordingly, so the host controller
> reads up to 255 bytes of uninitialised memory and sends it to the device,
> and can read past the end of the buffer as well.
>
> Patch 2 fixes that by padding the SKB with zeros. The padding is written
> behind skb->tail, which is only safe once the driver owns the data
> buffer, so patch 1 replaces the open-coded headroom check with
> skb_cow_head() first. Patch 1 on its own changes no observable
> behaviour, but it is a hard prerequisite, so both patches carry the same
> Fixes: tag.
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: btmtksdio: Take exclusive ownership of the SKB before TX
https://git.kernel.org/bluetooth/bluetooth-next/c/951d9f743029
- [2/2] Bluetooth: btmtksdio: Fix out-of-bounds DMA read in the TX path
https://git.kernel.org/bluetooth/bluetooth-next/c/262cb784c96c
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-08-17 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 9:53 [PATCH 0/2] Bluetooth: btmtksdio: Fix SKB handling in the TX path Chris Lu
2026-08-17 9:53 ` [PATCH 1/2] Bluetooth: btmtksdio: Take exclusive ownership of the SKB before TX Chris Lu
2026-08-17 9:53 ` [PATCH 2/2] Bluetooth: btmtksdio: Fix out-of-bounds DMA read in the TX path Chris Lu
2026-08-17 19:45 ` 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=178699595738.1691257.9499694982738760170.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chris.lu@mediatek.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=sean.wang@mediatek.com \
--cc=ss.wu@mediatek.com \
--cc=will-cy.Lee@mediatek.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