From: patchwork-bot+bluetooth@kernel.org
To: Sangho Lee <kudo3228@gmail.com>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org,
linux-bluetooth@vger.kernel.org, jikos@kernel.org,
alan@signal11.us, padovan@profusion.mobi,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] Bluetooth: HIDP: validate short receive frames
Date: Fri, 24 Jul 2026 19:00:08 +0000 [thread overview]
Message-ID: <178491960889.3273549.17393254757476094302.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260723032807.1616487-1-kudo3228@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 23 Jul 2026 12:28:05 +0900 you wrote:
> The HIDP control and interrupt receive paths assume that every L2CAP SDU
> contains a transaction header. The raw-report return path also assumes that
> a numbered DATA response contains a report ID. Both assumptions allow a
> connected peer to make HIDP consume data beyond the logical skb boundary.
>
> The tests used two BlueZ 5.87 btvirt BR/EDR controllers, real L2CAP PSM
> 0x11/0x13 channels, HIDPCONNADD, and HIDIOCGFEATURE on bluetooth.git at
> df541cd485ff. The series also applies without changes to bluetooth-next at
> 6f55ad8fb0ac.
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: HIDP: reject frames without a transaction header
https://git.kernel.org/bluetooth/bluetooth-next/c/678c435909f2
- [2/2] Bluetooth: HIDP: validate numbered report payloads
https://git.kernel.org/bluetooth/bluetooth-next/c/883532b7d4eb
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-07-24 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 3:28 [PATCH 0/2] Bluetooth: HIDP: validate short receive frames Sangho Lee
2026-07-23 3:28 ` [PATCH 1/2] Bluetooth: HIDP: reject frames without a transaction header Sangho Lee
2026-07-23 4:58 ` Bluetooth: HIDP: validate short receive frames bluez.test.bot
2026-07-23 3:28 ` [PATCH 2/2] Bluetooth: HIDP: validate numbered report payloads Sangho Lee
2026-07-24 19:00 ` 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=178491960889.3273549.17393254757476094302.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alan@signal11.us \
--cc=jikos@kernel.org \
--cc=kudo3228@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=padovan@profusion.mobi \
--cc=stable@vger.kernel.org \
/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