linux-kernel - Re: [RESEND PATCH v1] Bluetooth: hci_uart: fix race during initialization

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: 
 <173989323376.4126041.7605697940734991168.git-patchwork-notify@kernel.org>
Date: Tue, 18 Feb 2025 15:40:33 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Arseniy Krasnov <avkrasnov@...utedevices.com>
Cc: marcel@...tmann.org, luiz.dentz@...il.com, oxffffaa@...il.com,
 linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
 kernel@...utedevices.com
Subject: Re: [RESEND PATCH v1] Bluetooth: hci_uart: fix race during initialization

Hello:

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

On Wed, 12 Feb 2025 18:59:46 +0300 you wrote:
> Do not set 'HCI_UART_PROTO_READY' before call 'hci_uart_register_dev()'.
> Possible race is when someone calls 'hci_tty_uart_close()' after this bit
> is set, but 'hci_uart_register_dev()' wasn't done. This leads to access
> to uninitialized fields. To fix it let's set this bit after device was
> registered (as before patch c411c62cc133) and to fix previous problem let's
> add one more bit in addition to 'HCI_UART_PROTO_READY' which allows to
> perform power up without original bit set (pls see commit c411c62cc133).
> 
> [...]

Here is the summary with links:
  - [RESEND,v1] Bluetooth: hci_uart: fix race during initialization
    https://git.kernel.org/bluetooth/bluetooth-next/c/e2040fe3b82b

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