Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Jinwang Li <jinwang.li@oss.qualcomm.com>
Cc: linux-bluetooth@vger.kernel.org, cheng.jiang@oss.qualcomm.com,
	wei.deng@oss.qualcomm.com, shuai.zhang@oss.qualcomm.com,
	xiuzhuo.shang@oss.qualcomm.com
Subject: Re: [PATCH BlueZ v4] avdtp: Fix use-after-free in connection_lost
Date: Wed, 18 Nov 2026 19:20:06 +0000	[thread overview]
Message-ID: <179502960678.2490531.3103046334132102769.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116090719.1226616-1-jinwang.li@oss.qualcomm.com>

Hello:

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

On Mon, 16 Nov 2026 17:07:19 +0800 you wrote:
> A sink may start reverse discovery when processing a remote stream
> configuration. If the signaling channel disconnects after the stream is
> configured and discovery holds the last setup reference, stream cleanup
> frees that setup before the pending discovery callback runs, causing a
> use-after-free.
> 
> Complete discovery with the disconnect error before releasing streams
> so the callback runs while its setup is still valid.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v4] avdtp: Fix use-after-free in connection_lost
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=43de1efcb453

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-11-18 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16  9:07 [PATCH BlueZ v4] avdtp: Fix use-after-free in connection_lost Jinwang Li
2026-11-16 21:48 ` [BlueZ,v4] " bluez.test.bot
2026-11-18 19:20 ` 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=179502960678.2490531.3103046334132102769.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=cheng.jiang@oss.qualcomm.com \
    --cc=jinwang.li@oss.qualcomm.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=shuai.zhang@oss.qualcomm.com \
    --cc=wei.deng@oss.qualcomm.com \
    --cc=xiuzhuo.shang@oss.qualcomm.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