linux-kernel - Re: [PATCH v3] Bluetooth: L2CAP: Fix slab-use-after-free in l2cap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <171448683038.20667.12009081489317667942.git-patchwork-notify@kernel.org>
Date: Tue, 30 Apr 2024 14:20:30 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Sungwoo Kim <iam@...g-woo.kim>
Cc: daveti@...due.edu, dan.carpenter@...aro.org, marcel@...tmann.org,
 johan.hedberg@...il.com, luiz.dentz@...il.com,
 linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] Bluetooth: L2CAP: Fix slab-use-after-free in
 l2cap_connect()

Hello:

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

On Tue, 30 Apr 2024 02:32:10 -0400 you wrote:
> Extend a critical section to prevent chan from early freeing.
> Also make the l2cap_connect() return type void. Nothing is using the
> returned value but it is ugly to return a potentially freed pointer.
> Making it void will help with backports because earlier kernels did use
> the return value. Now the compile will break for kernels where this
> patch is not a complete fix.
> 
> [...]

Here is the summary with links:
  - [v3] Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()
    https://git.kernel.org/bluetooth/bluetooth-next/c/6a39d26feb15

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