From: patchwork-bot+bluetooth@kernel.org
To: Maiquel Paiva <maiquelpaiva@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
gregkh@linuxfoundation.org, marcel@holtmann.org
Subject: Re: [PATCH v4 0/2] Bluetooth: mgmt: Fix heap overflow and race condition
Date: Mon, 09 Feb 2026 20:00:04 +0000 [thread overview]
Message-ID: <177066720482.3196175.13167614416923442442.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260208081559.44983-1-maiquelpaiva@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 8 Feb 2026 08:15:57 +0000 you wrote:
> This series fixes two vulnerabilities found in net/bluetooth/mgmt_util.c related to mesh handling.
>
> Patch 1 addresses a heap buffer overflow in mgmt_mesh_add by validating the user-provided length.
> Patch 2 resolves race conditions in mgmt_mesh_add and mgmt_mesh_find by protecting the list operations.
>
> Changes in v4:
> - Replaced guard(mutex) with guard(spinlock) using hdev->lock in Patch 2.
> - This fixes the "sleeping function called from invalid context" and circular locking warnings reported by the CI robot in v3.
>
> [...]
Here is the summary with links:
- [v4,1/2] Bluetooth: mgmt: Fix heap overflow in mgmt_mesh_add
(no matching commit)
- [v4,2/2] Bluetooth: mgmt: Fix race conditions in mesh handling
https://git.kernel.org/bluetooth/bluetooth-next/c/567233b63ddb
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-02-09 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 8:15 [PATCH v4 0/2] Bluetooth: mgmt: Fix heap overflow and race condition Maiquel Paiva
2026-02-08 8:15 ` [PATCH v4 1/2] Bluetooth: mgmt: Fix heap overflow in mgmt_mesh_add Maiquel Paiva
2026-02-08 8:43 ` Bluetooth: mgmt: Fix heap overflow and race condition bluez.test.bot
2026-02-08 8:15 ` [PATCH v4 2/2] Bluetooth: mgmt: Fix race conditions in mesh handling Maiquel Paiva
2026-02-08 12:57 ` kernel test robot
2026-02-08 12:57 ` kernel test robot
2026-02-09 19:44 ` Luiz Augusto von Dentz
2026-02-09 20: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=177066720482.3196175.13167614416923442442.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=maiquelpaiva@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