public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Wang Tao <wangtao554@huawei.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org, zhangqiao22@huawei.com,
	tanghui20@huawei.com
Subject: Re: [PATCH] Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers
Date: Fri, 06 Mar 2026 03:33:08 +0000	[thread overview]
Message-ID: <177276798804.3348267.17252106352846534808.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260227110339.919014-1-wangtao554@huawei.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Fri, 27 Feb 2026 11:03:39 +0000 you wrote:
> Commit 302a1f674c00 ("Bluetooth: MGMT: Fix possible UAFs") introduced
> mgmt_pending_valid(), which not only validates the pending command but
> also unlinks it from the pending list if it is valid. This change in
> semantics requires updates to several completion handlers to avoid list
> corruption and memory safety issues.
> 
> This patch addresses two left-over issues from the aforementioned rework:
> 
> [...]

Here is the summary with links:
  - Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers
    https://git.kernel.org/bluetooth/bluetooth-next/c/eaf573d74cd1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-03-06  3:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 11:03 [PATCH] Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers Wang Tao
2026-02-27 12:15 ` bluez.test.bot
2026-03-06  3:33 ` 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=177276798804.3348267.17252106352846534808.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=tanghui20@huawei.com \
    --cc=wangtao554@huawei.com \
    --cc=zhangqiao22@huawei.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