CVE-2026-68085
Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled
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.
INFO
Published Date :
Aug. 10, 2026, 12:17 p.m.
Last Modified :
Aug. 10, 2026, 12:17 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-68085
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Clear HCI_UART_SENDING bit when canceling write work.
- Use disable_work_sync and enable_work for safe clearing.
- Cancel pending work in hci_uart_flush() function.
- Re-enable and requeue work after queue flush.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-68085.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-68085 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-68085
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-68085 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-68085 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 10, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '81c7a3c22a0f2808cf4ae0b4908f59763b23606d', 'lessThan': 'd52446b3e735cfdbdc2a58342163803bc2e64249', 'versionType': 'git'}, {'status': 'affected', 'version': '192cb0f1ca706d9a1bc36ae0ad5f666d1e4fd894', 'lessThan': 'b9dd39cf1667e378b25a082ca796d495d578c5d3', 'versionType': 'git'}, {'status': 'affected', 'version': 'c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b', 'lessThan': '714d861d35d937f23375a4517569b13917bbbe51', 'versionType': 'git'}, {'status': 'affected', 'version': 'c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b', 'lessThan': '1b0d946d6f08bd39211385bc703a440911b41e46', 'versionType': 'git'}, {'status': 'affected', 'version': '78aad93e938f013d9272fe0ee168f27883afa95c', 'versionType': 'git'}, {'status': 'affected', 'version': 'e2d19969c8d9198ecc3090bcd5312ecd503a3339', 'versionType': 'git'}, {'status': 'affected', 'version': 'c85cff648a2bc92322912db5f1727ad05afae7b6', 'versionType': 'git'}, {'status': 'affected', 'version': '9d20d48be2c4a071fb015eb09bda2cecd25daf34', 'versionType': 'git'}, {'status': 'affected', 'version': '7338031946bd06f6dff149e67b60c4cd083bfea8', 'versionType': 'git'}, {'status': 'affected', 'version': '6.12.92', 'lessThan': '6.12.96', 'versionType': 'semver'}, {'status': 'affected', 'version': '6.18.34', 'lessThan': '6.18.39', 'versionType': 'semver'}, {'status': 'affected', 'version': '5.10.258', 'lessThan': '5.11', 'versionType': 'semver'}, {'status': 'affected', 'version': '5.15.209', 'lessThan': '5.16', 'versionType': 'semver'}, {'status': 'affected', 'version': '6.1.175', 'lessThan': '6.2', 'versionType': 'semver'}, {'status': 'affected', 'version': '6.6.142', 'lessThan': '6.7', 'versionType': 'semver'}, {'status': 'affected', 'version': '7.0.11', 'lessThan': '7.1', 'versionType': 'semver'}], 'programFiles': ['drivers/bluetooth/hci_ldisc.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '7.1'}, {'status': 'unaffected', 'version': '0', 'lessThan': '7.1', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.12.96', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.39', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.4', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc3', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/bluetooth/hci_ldisc.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/1b0d946d6f08bd39211385bc703a440911b41e46 Added Reference https://git.kernel.org/stable/c/714d861d35d937f23375a4517569b13917bbbe51 Added Reference https://git.kernel.org/stable/c/b9dd39cf1667e378b25a082ca796d495d578c5d3 Added Reference https://git.kernel.org/stable/c/d52446b3e735cfdbdc2a58342163803bc2e64249