From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 0/8] Fix handling of malformed GATT PDUs
Date: Sat, 07 Nov 2026 21:00:06 +0000 [thread overview]
Message-ID: <179408520642.1337848.1745297927626770621.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106183350.3155282-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 6 Nov 2026 13:33:42 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This fixes several places where GATT PDUs received from the peer are
> used without proper validation:
>
> - Read By Type responses with an invalid Attribute Data Length could
> cause a division by zero and out-of-bounds reads during discovery.
> - Notifications and indications shorter than a handle wrapped the
> value length to 65534, passing data past the received buffer to the
> registered handlers.
> - Read Multiple Variable Length opcodes were missing from the ATT
> tables, so the server never responded to the request, and the
> client response parser did not advance past each value.
> - Database Hash and Extended Properties values were read without
> checking their length.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/8] shared/gatt: Validate Read By Type responses
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=02acfdbe0374
- [BlueZ,v2,2/8] unit/test-gatt: Add malformed Read By Type response tests
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=730d0138bf30
- [BlueZ,v2,3/8] shared/gatt-client: Fix handling of short notifications
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2d41b1aab0b8
- [BlueZ,v2,4/8] unit/test-gatt: Add short notification test
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ea2ab6628b8d
- [BlueZ,v2,5/8] shared/att: Add Read Multiple Variable Length opcodes
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0c2f60273e63
- [BlueZ,v2,6/8] shared/gatt-client: Fix parsing Read Multiple Variable Length response
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3b15e6d5bb70
- [BlueZ,v2,7/8] shared/gatt-client: Check value lengths before reading them
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=bf1fd8831d56
- [BlueZ,v2,8/8] unit/test-gatt: Add Read Multiple Variable Length tests
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=aa4f5ce97c87
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-11-07 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 18:33 [PATCH BlueZ v2 0/8] Fix handling of malformed GATT PDUs Luiz Augusto von Dentz
2026-11-06 18:33 ` [PATCH BlueZ v2 1/8] shared/gatt: Validate Read By Type responses Luiz Augusto von Dentz
2026-11-06 23:18 ` Fix handling of malformed GATT PDUs bluez.test.bot
2026-11-06 18:33 ` [PATCH BlueZ v2 2/8] unit/test-gatt: Add malformed Read By Type response tests Luiz Augusto von Dentz
2026-11-06 18:33 ` [PATCH BlueZ v2 3/8] shared/gatt-client: Fix handling of short notifications Luiz Augusto von Dentz
2026-11-06 18:33 ` [PATCH BlueZ v2 4/8] unit/test-gatt: Add short notification test Luiz Augusto von Dentz
2026-11-06 18:33 ` [PATCH BlueZ v2 5/8] shared/att: Add Read Multiple Variable Length opcodes Luiz Augusto von Dentz
2026-11-06 18:33 ` [PATCH BlueZ v2 6/8] shared/gatt-client: Fix parsing Read Multiple Variable Length response Luiz Augusto von Dentz
2026-11-06 18:33 ` [PATCH BlueZ v2 7/8] shared/gatt-client: Check value lengths before reading them Luiz Augusto von Dentz
2026-11-06 18:33 ` [PATCH BlueZ v2 8/8] unit/test-gatt: Add Read Multiple Variable Length tests Luiz Augusto von Dentz
2026-11-07 21: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=179408520642.1337848.1745297927626770621.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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