From: patchwork-bot+bluetooth@kernel.org
To: Keenan Dong <keenanat2000@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: MGMT: validate mesh send advertising payload length
Date: Wed, 01 Apr 2026 18:30:04 +0000 [thread overview]
Message-ID: <177506820429.3813163.15864121769222548802.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260401142532.332943-1-keenanat2000@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 1 Apr 2026 22:25:26 +0800 you wrote:
> mesh_send() currently bounds MGMT_OP_MESH_SEND by total command
> length, but it never verifies that the bytes supplied for the
> flexible adv_data[] array actually match the embedded adv_data_len
> field. MGMT_MESH_SEND_SIZE only covers the fixed header, so a
> truncated command can still pass the existing 20..50 byte range
> check and later drive the async mesh send path past the end of the
> queued command buffer.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: MGMT: validate mesh send advertising payload length
https://git.kernel.org/bluetooth/bluetooth-next/c/2c12536623ca
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-04-01 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 8:46 [PATCH] Bluetooth: MGMT: validate LTK enc_size on load Keenan Dong
2026-03-28 8:46 ` [PATCH] Bluetooth: MGMT: require exact mesh send payload length Keenan Dong
2026-03-28 9:53 ` bluez.test.bot
2026-03-30 20:06 ` [PATCH] " Luiz Augusto von Dentz
2026-04-01 14:52 ` Keenan Dong
2026-04-01 14:25 ` [PATCH v2] Bluetooth: MGMT: validate mesh send advertising " Keenan Dong
2026-04-01 15:10 ` [v2] " bluez.test.bot
2026-04-01 18:30 ` patchwork-bot+bluetooth [this message]
2026-03-28 9:52 ` Bluetooth: MGMT: validate LTK enc_size on load bluez.test.bot
2026-03-30 20:20 ` [PATCH] " patchwork-bot+bluetooth
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=177506820429.3813163.15864121769222548802.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=keenanat2000@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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