From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] transport: Fix use-after-free when replacing a linked transport's owner
Date: Wed, 02 Sep 2026 15:40:07 +0000 [thread overview]
Message-ID: <178836360763.2802406.9178353804129746486.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260831144556.128154-1-frederic.danis@collabora.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 31 Aug 2026 16:45:56 +0200 you wrote:
> linked_transport_set_owner() unconditionally overwrote a linked
> transport's owner pointer. If that transport already had a different
> owner assigned (e.g. its own Acquire request was still pending when the
> paired transport's owner was set), the previous media_owner was
> orphaned: its D-Bus disconnect watch stayed registered and its
> ->transport back-pointer kept pointing at the transport. Once the
> transport was later destroyed, the still-registered watch would
> eventually fire media_owner_exit() and dereference the freed transport.
>
> [...]
Here is the summary with links:
- [BlueZ] transport: Fix use-after-free when replacing a linked transport's owner
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a03665b6dd20
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-09-02 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 14:45 [PATCH BlueZ] transport: Fix use-after-free when replacing a linked transport's owner Frédéric Danis
2026-08-31 15:51 ` [BlueZ] " bluez.test.bot
2026-09-02 15: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=178836360763.2802406.9178353804129746486.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--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