From: patchwork-bot+bluetooth@kernel.org
To: Weiming Shi <bestswngs@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
armansito@chromium.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, xmei5@asu.edu
Subject: Re: [PATCH v2] Bluetooth: eir: Fix stack OOB write when prepending the Flags AD
Date: Wed, 03 Jun 2026 17:50:09 +0000 [thread overview]
Message-ID: <178050900939.1520440.11240262653174348549.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260602170621.1454711-2-bestswngs@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, 3 Jun 2026 01:06:21 +0800 you wrote:
> eir_create_adv_data() builds the advertising data into a fixed-size
> buffer ("size", 31 for the legacy path). It may prepend a 3-byte "Flags"
> AD structure (LE_AD_NO_BREDR on an LE-only controller) and then copies
> the per-instance data without checking that it still fits:
>
> memcpy(ptr, adv->adv_data, adv->adv_data_len);
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: eir: Fix stack OOB write when prepending the Flags AD
https://git.kernel.org/bluetooth/bluetooth-next/c/83dc982fad52
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-06-03 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 17:06 [PATCH v2] Bluetooth: eir: Fix stack OOB write when prepending the Flags AD Weiming Shi
2026-06-02 19:14 ` [v2] " bluez.test.bot
2026-06-03 17:50 ` 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=178050900939.1520440.11240262653174348549.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=armansito@chromium.org \
--cc=bestswngs@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=xmei5@asu.edu \
/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