From: patchwork-bot+bluetooth@kernel.org
To: Lasse Dalegaard <dalegaard@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] gatt-client: fix use-after-free
Date: Fri, 09 Jan 2026 22:40:08 +0000 [thread overview]
Message-ID: <176799840802.418288.2490552133540190635.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260108100136.486675-1-dalegaard@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 8 Jan 2026 11:01:35 +0100 you wrote:
> Clients with an acquired characteristic subscription would free the
> client during disconnect. When notify_io_destroy then tries to remove
> the client, it'll use-after-free.
>
> Add another reference when allocating the notify_io and unref it again
> in notify_io_destroy.
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] gatt-client: fix use-after-free
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a94f994201a6
- [BlueZ,2/2] device: fix memory leak
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=024b148d73ae
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-01-09 22:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 10:01 [PATCH BlueZ 1/2] gatt-client: fix use-after-free Lasse Dalegaard
2026-01-08 10:01 ` [PATCH BlueZ 2/2] device: fix memory leak Lasse Dalegaard
2026-01-08 15:27 ` Luiz Augusto von Dentz
2026-01-08 18:50 ` Lasse Dalegaard
2026-01-08 19:08 ` Luiz Augusto von Dentz
2026-01-08 11:10 ` [BlueZ,1/2] gatt-client: fix use-after-free bluez.test.bot
2026-01-08 15:23 ` [PATCH BlueZ 1/2] " Luiz Augusto von Dentz
2026-01-08 18:46 ` Lasse Dalegaard
2026-01-08 19:06 ` Luiz Augusto von Dentz
2026-01-09 22: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=176799840802.418288.2490552133540190635.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=dalegaard@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox