linux-kernel - Re: [PATCH] Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan

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: 
 <171475562973.29614.6591900788209831933.git-patchwork-notify@kernel.org>
Date: Fri, 03 May 2024 17:00:29 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Duoming Zhou <duoming@....edu.cn>
Cc: linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
 luiz.dentz@...il.com, johan.hedberg@...il.com, marcel@...tmann.org
Subject: Re: [PATCH] Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout

Hello:

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

On Thu,  2 May 2024 20:57:36 +0800 you wrote:
> There is a race condition between l2cap_chan_timeout() and
> l2cap_chan_del(). When we use l2cap_chan_del() to delete the
> channel, the chan->conn will be set to null. But the conn could
> be dereferenced again in the mutex_lock() of l2cap_chan_timeout().
> As a result the null pointer dereference bug will happen. The
> KASAN report triggered by POC is shown below:
> 
> [...]

Here is the summary with links:
  - Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout
    https://git.kernel.org/bluetooth/bluetooth-next/c/8192cea84c6c

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