{"id":"CVE-2026-98297","published":"2026-10-06T09:18:20.400","lastModified":"2026-10-06T09:18:20.400","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: Fix queuing tx_work after workqueue is drained\n\nhci_send_acl(), hci_send_sco() and hci_send_iso() queue hdev->tx_work\nunconditionally. They can run from the L2CAP/SCO/ISO socket send path\nwhile hci_dev_close_sync() is draining hdev->workqueue (HCIDEVDOWN\nracing with a socket write). Since that queue_work() is not chained\nwork from the tx_work worker itself, __queue_work() sees the queue\nmarked __WQ_DRAINING, warns \"cannot queue %ps on wq %s\", and drops\nthe work:\n\n  WARNING: CPU: 1 PID: 5985 at kernel/workqueue.c:2352 __queue_work\n  Call Trace:\n   queue_work_on\n   l2cap_chan_send\n   l2cap_sock_sendmsg\n   ...\n\nhci_dev_close_sync() already sets HCI_CMD_DRAIN_WORKQUEUE before\ndraining, but only hci_cmd_work() and handle_cmd_cnt_and_timer()\ncheck it before queuing. Route the tx_work producers through the\nsame guard via a shared hci_sched_tx() helper.","cvssScore":null,"cvssSeverity":null,"cvssVector":null,"cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/6610c6fe4b8936c232048e6049bf77c70a6f759c","tags":[]},{"url":"https://git.kernel.org/stable/c/ab0678a0701ac4de499428dc1b321659bb74d272","tags":[]},{"url":"https://git.kernel.org/stable/c/cbb325bc150e8c0dbce004ac0e5516bcffc0de31","tags":[]},{"url":"https://git.kernel.org/stable/c/e220c1242a643d97102a79f09b7ef3aa31276961","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}