linux-kernel - Re: [PATCH] Bluetooth: qca: fix invalid device address check

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] [thread-next>] [day] [month] [year] [list]

Message-Id: 
 <171328023410.16225.6796027488142953241.git-patchwork-notify@kernel.org>
Date: Tue, 16 Apr 2024 15:10:34 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Johan Hovold <johan+linaro@...nel.org>
Cc: marcel@...tmann.org, luiz.dentz@...il.com, mka@...omium.org,
 dianders@...omium.org, linux-bluetooth@...r.kernel.org,
 linux-kernel@...r.kernel.org, quic_janathot@...cinc.com,
 stable@...r.kernel.org
Subject: Re: [PATCH] Bluetooth: qca: fix invalid device address check

Hello:

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

On Tue, 16 Apr 2024 11:15:09 +0200 you wrote:
> Qualcomm Bluetooth controllers may not have been provisioned with a
> valid device address and instead end up using the default address
> 00:00:00:00:5a:ad.
> 
> This was previously believed to be due to lack of persistent storage for
> the address but it may also be due to integrators opting to not use the
> on-chip OTP memory and instead store the address elsewhere (e.g. in
> storage managed by secure world firmware).
> 
> [...]

Here is the summary with links:
  - Bluetooth: qca: fix invalid device address check
    https://git.kernel.org/bluetooth/bluetooth-next/c/00567f70051a

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