linux-kernel - Re: [PATCH] Bluetooth: btintel: Add devices to HCI_QUIRK_BROKEN_LE

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]

Date: Tue, 02 Apr 2024 11:17:45 +0200
From: Christoffer Sandberg <cs@...edo.de>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: Werner Sembach <wse@...edocomputers.com>, Marcel Holtmann
 <marcel@...tmann.org>, Luiz Augusto von Dentz <luiz.dentz@...il.com>,
 Christoffer Sandberg <cs@...edo.de>, linux-bluetooth@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Bluetooth: btintel: Add devices to
 HCI_QUIRK_BROKEN_LE_CODED

Dear Paul,

On 28.3.2024 14:23, Paul Menzel wrote:
> On what hardware with what clients do you experience this exactly?
> 

The wifi/bluetooth modules AX201, AX210 and AX211 (cases 0x18, 0x17 and 
0x19 respectively) used in various notebook devices started having 
issues as of the patch that enabled le coded phy in the driver. (We also 
use AX200, however without issue.)

Noted behaviour as of the issues: Device scan took longer and when it 
did find a device connection often failed or timed out.

I do not know if a special type of bluetooth client is affected. It was 
partially tested by looking at the difference in enumeration of the 
current mix of bluetooth clients in the area (where you could clearly 
see the difference at a glance) and with one specific device.  A 
bluetooth connected watercooling system (TUXEDO Aquaris or 
LCT21001/LCT22002) where a test case showed the mentioned issues.

Best regards,

Christoffer