From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ 0/2] adv_monitor: Fix buffer overflow caused by integer overflow
Date: Fri, 14 Aug 2026 17:20:12 +0000 [thread overview]
Message-ID: <178672801263.3885098.12402993534569851547.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813091937.2600061-1-hadess@hadess.net>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 13 Aug 2026 11:16:56 +0200 you wrote:
> Those issues were originally reported as security issues, but we not
> deemed worthy of a security advisory as they impacted an experimental
> feature.
>
> Bastien Nocera (2):
> adv_monitor: Fix buffer overflow caused by integer overflow
> adv_monitor: Ignore additional patterns past what's supported
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] adv_monitor: Fix buffer overflow caused by integer overflow
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5cf94acaea71
- [BlueZ,2/2] adv_monitor: Ignore additional patterns past what's supported
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=14347c86fb99
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-14 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 9:16 [BlueZ 0/2] adv_monitor: Fix buffer overflow caused by integer overflow Bastien Nocera
2026-08-13 9:16 ` [BlueZ 1/2] " Bastien Nocera
2026-08-13 10:30 ` bluez.test.bot
2026-08-13 9:16 ` [BlueZ 2/2] adv_monitor: Ignore additional patterns past what's supported Bastien Nocera
2026-08-14 17:20 ` 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=178672801263.3885098.12402993534569851547.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.