CVE-2026-68085

Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled

HIGH
8
CVSS Score
Published: August 10, 2026 at 11:51 AM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

192cb0f1ca706d9a1bc36ae0ad5f666d1e4fd8945.10.2585.15.2096.1.1756.12.926.18.346.6.1427.0.117.17338031946bd06f6dff149e67b60c4cd083bfea878aad93e938f013d9272fe0ee168f27883afa95c81c7a3c22a0f2808cf4ae0b4908f59763b23606d9d20d48be2c4a071fb015eb09bda2cecd25daf34c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429bc85cff648a2bc92322912db5f1727ad05afae7b6e2d19969c8d9198ecc3090bcd5312ecd503a3339
Vendor states this is fixed in 1b0d946d6f08bd39211385bc703a440911b41e46 (fixed)
Vendor states this is fixed in 714d861d35d937f23375a4517569b13917bbbe51 (fixed)
Vendor states this is fixed in b9dd39cf1667e378b25a082ca796d495d578c5d3 (fixed)
Vendor states this is fixed in d52446b3e735cfdbdc2a58342163803bc2e64249 (fixed)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.1 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card