Fix bluetooth connections with 3.0 device
Bug #2063067 reported by
AaronMa
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
In Progress
|
High
|
AaronMa | ||
linux (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Mantic |
Fix Released
|
High
|
Unassigned | ||
linux-oem-6.5 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Unassigned | ||
Mantic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Bluetooth keyboard cannot be connected to Realtek BT controller.
[Fix]
It's a regression from Ubuntu-6.5.0-20.20 and Ubuntu-
The bad commit:
c7f59461f5a78 ("Bluetooth: Fix a refcnt underflow problem for hci_conn")
Fix:
7e74aa53a68bf ("Bluetooth: hci_event: Fix handling of HCI_EV_
[Test]
Tested on hardware, the bt3.0 keyboard connects to host well.
[Where problems could occur]
It may break bluetooth.
The commit is already in v6.8-rc7,
SRU Jammy, oem-6.5 and Mantic.
CVE References
- 2023-47233
- 2023-52447
- 2023-52530
- 2023-52601
- 2023-52880
- 2023-6270
- 2024-21823
- 2024-2201
- 2024-23307
- 2024-24861
- 2024-26583
- 2024-26584
- 2024-26585
- 2024-26593
- 2024-26614
- 2024-26622
- 2024-26635
- 2024-26642
- 2024-26643
- 2024-26694
- 2024-26704
- 2024-26710
- 2024-26712
- 2024-26733
- 2024-26734
- 2024-26735
- 2024-26736
- 2024-26748
- 2024-26782
- 2024-26789
- 2024-26790
- 2024-26792
- 2024-26798
- 2024-26801
- 2024-26802
- 2024-26803
- 2024-26805
- 2024-26809
- 2024-26838
- 2024-26889
- 2024-26890
- 2024-26922
- 2024-26923
- 2024-26924
- 2024-26925
- 2024-26926
- 2024-52602
- 2024-52615
tags: | added: oem-priority originate-from-2058356 sutton |
Changed in linux-oem-6.5 (Ubuntu Mantic): | |
status: | New → Invalid |
Changed in linux (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in linux (Ubuntu Mantic): | |
status: | New → In Progress |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in hwe-next: | |
assignee: | nobody → AaronMa (mapengyu) |
importance: | Undecided → High |
Changed in linux (Ubuntu Mantic): | |
importance: | Undecided → High |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
importance: | Undecided → High |
Changed in hwe-next: | |
status: | New → In Progress |
description: | updated |
Changed in linux (Ubuntu Jammy): | |
status: | Invalid → In Progress |
description: | updated |
Changed in linux (Ubuntu Mantic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-6.5 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-focal-linux-azure-5.15 verification-done-jammy-linux-azure-fips verification-done-jammy-linux-oem-6.5 removed: verification-needed-focal-linux-azure-5.15 verification-needed-jammy-linux-azure-fips verification-needed-jammy-linux-oem-6.5 |
tags: |
added: verification-done-focal-linux-intel-iotg-5.15 removed: verification-needed-focal-linux-intel-iotg-5.15 |
tags: |
added: verification-done-focal-linux-hwe-5.15 verification-done-mantic-linux removed: verification-needed-focal-linux-hwe-5.15 verification-needed-mantic-linux |
To post a comment you must log in.
This bug is awaiting verification that the linux/5. 15.0-111. 121 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- jammy-linux' to 'verification- done-jammy- linux'. If the problem still exists, change the tag 'verification- needed- jammy-linux' to 'verification- failed- jammy-linux' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!