All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Andreas Kemnade <andreas@kemnade.info>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] gatt-client: avoid UAF after acquire notify failure
Date: Tue, 01 Jul 2025 20:10:06 +0000	[thread overview]
Message-ID: <175140060651.104274.14105034226094335996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250630143933.1658224-1-andreas@kemnade.info>

Hello:

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

On Mon, 30 Jun 2025 16:39:33 +0200 you wrote:
> If a disconnect happens during AcquireNotify dbus calls, a lot of
> debris is left over. Subsequent calls to AcquireNotify will return
> NotPermitted and StopNotify leads to an UAF, crashing bluetoothd.
> 
> Fix that by also clean up the socket stuff on failure.
> 
> This was provoked by putting the device into some RF shielding bag
> and open and close it quickly.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2] gatt-client: avoid UAF after acquire notify failure
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=476ae809a27e

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



      parent reply	other threads:[~2025-07-01 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 14:39 [PATCH BlueZ v2] gatt-client: avoid UAF after acquire notify failure Andreas Kemnade
2025-06-30 16:07 ` [BlueZ,v2] " bluez.test.bot
2025-07-01 20:10 ` 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=175140060651.104274.14105034226094335996.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=andreas@kemnade.info \
    --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.