From: patchwork-bot+bluetooth@kernel.org
To: Ren Wei <enjou1224z@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, padovan@profusion.mobi,
johan.hedberg@nokia.com, vega@nebusec.ai, xizh2024@lzu.edu.cn
Subject: Re: [PATCH 0/1] Bluetooth: mgmt: fix pairing command UAF
Date: Tue, 21 Jul 2026 19:40:32 +0000 [thread overview]
Message-ID: <178466283291.1001510.16769064007177227077.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1784492458.git.xizh2024@lzu.edu.cn>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 21 Jul 2026 22:36:06 +0800 you wrote:
> From: Zihan Xi <xizh2024@lzu.edu.cn>
>
>
> Hi Linux kernel maintainers,
>
> We found and validated a bug in net/bluetooth/mgmt.c. The bug is
> reachable by a privileged local user through the Bluetooth management
> interface when a Pair Device command races with pairing failure and
> cancellation paths. The fixed kernel was run with the reproducer for
> 420 seconds and then for 1200 seconds without the original KASAN
> use-after-free, list_debug BUG, or panic. The reproducer did not
> naturally finish before the timeout in those fixed-kernel runs.
>
> [...]
Here is the summary with links:
- [1/1] Bluetooth: mgmt: fix UAF in pair command cancellation
https://git.kernel.org/bluetooth/bluetooth-next/c/300a6fb2d8b7
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-07-21 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 14:36 [PATCH 0/1] Bluetooth: mgmt: fix pairing command UAF Ren Wei
2026-07-21 14:36 ` [PATCH 1/1] Bluetooth: mgmt: fix UAF in pair command cancellation Ren Wei
2026-07-21 15:21 ` Bluetooth: mgmt: fix pairing command UAF bluez.test.bot
2026-07-21 19:40 ` 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=178466283291.1001510.16769064007177227077.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=enjou1224z@gmail.com \
--cc=johan.hedberg@nokia.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=padovan@profusion.mobi \
--cc=vega@nebusec.ai \
--cc=xizh2024@lzu.edu.cn \
/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.