[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170473682437.30343.8024937175045116311.git-patchwork-notify@kernel.org>
Date: Mon, 08 Jan 2024 18:00:24 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Yuxuan-Hu <20373622@...a.edu.cn>
Cc: marcel@...tmann.org, johan.hedberg@...il.com, luiz.dentz@...il.com,
linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
baijiaju1990@...il.com, sy2239101@...a.edu.cn, pmenzel@...gen.mpg.de
Subject: Re: [PATCH V3] Bluetooth: rfcomm: Fix null-ptr-deref in
rfcomm_check_security
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:
On Wed, 3 Jan 2024 17:10:43 +0800 you wrote:
> During our fuzz testing of the connection and disconnection process at the
> RFCOMM layer, we discovered this bug. By comparing the packets from a
> normal connection and disconnection process with the testcase that
> triggered a KASAN report. We analyzed the cause of this bug as follows:
>
> 1. In the packets captured during a normal connection, the host sends a
> `Read Encryption Key Size` type of `HCI_CMD` packet
> (Command Opcode: 0x1408) to the controller to inquire the length of
> encryption key.After receiving this packet, the controller immediately
> replies with a Command Completepacket (Event Code: 0x0e) to return the
> Encryption Key Size.
>
> [...]
Here is the summary with links:
- [V3] Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security
https://git.kernel.org/bluetooth/bluetooth-next/c/6ec00b0737fe
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists