Here's a proposed fix for this problem based on the current master-next of https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble
** Patch added: "0001-Bluetooth-hci_sync-fix-HCI_CMD_DRAIN_WORKQUEUE-fix.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167919/+attachment/6001646/+files/0001-Bluetooth-hci_sync-fix-HCI_CMD_DRAIN_WORKQUEUE-fix.patch ** Description changed: While investigating a bug in the derivative kernel (linux-qcom), I found out that the backport of this upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=525daaea459fc215f432de1b8debbd9144bf97b0 is broken in the Noble kernel. The patch was supposed to set the flag - HCI_CMD_DRAIN_WORKQUEUE at the beginning of the `hci_dev_close_sync()` + HCI_CMD_DRAIN_WORKQUEUE at the beginning of the `hci_dev_close_sync` (and clear it before finishing it). But instead in our tree this was - added at the beginning of the `hci_dev_open_sync()` which completely - broke the `hci_cmd_timeout()` functionality (as the flag would always be - set). + added at the beginning of the `hci_dev_open_sync` which completely broke + the `hci_cmd_timeout` functionality (as the flag would always be set). The issue was introduced in fd719dc6e35c2278fc9e6986e9333024de2a6d26 as part of https://bugs.launchpad.net/bugs/2161547. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167919 Title: Incorrect backport of the fix for CVE-2026-63974 to Noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167919/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
