Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] Bluetooth: L2CAP: Fix potential user-after-free
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <167537281732.11585.11132759600776902969.git-patchwork-notify@kernel.org>
Date:   Thu, 02 Feb 2023 21:20:17 +0000
References: <20230201220704.1543663-1-luiz.dentz@gmail.com>
In-Reply-To: <20230201220704.1543663-1-luiz.dentz@gmail.com>
To:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org
Precedence: bulk

Hello:

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

On Wed,  1 Feb 2023 14:07:03 -0800 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This fixes all instances of which requires to allocate a buffer calling
> alloc_skb which may release the chan lock and reacquire later which
> makes it possible that the chan is disconnected in the meantime.
> 
> Fixes: a6a5568c03c4 ("Bluetooth: Lock the L2CAP channel when sending")
> Reported-by: Alexander Coffin <alex.coffin@matician.com>
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> [...]

Here is the summary with links:
  - Bluetooth: L2CAP: Fix potential user-after-free
    https://git.kernel.org/bluetooth/bluetooth-next/c/c076b7d4e311

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