CVE-2026-68085
CVE-2026-68085 is a high-severity vulnerability with a CVSS 3.x base score of 8.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-667.
Key facts
- Severity: High (CVSS 3.x base score 8.0)
- EPSS exploit prediction: 0% (9th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-667
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2026-68085?
- 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.
- How severe is CVE-2026-68085?
- CVE-2026-68085 has a CVSS 3.x base score of 8.0, rated high severity. It is exploitable over an adjacent network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2026-68085 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-68085?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2026-68085 published?
- CVE-2026-68085 was published on 2026-08-10 and last updated on 2026-10-19.
References
- https://git.kernel.org/stable/c/1b0d946d6f08bd39211385bc703a440911b41e46
- https://git.kernel.org/stable/c/714d861d35d937f23375a4517569b13917bbbe51
- https://git.kernel.org/stable/c/b9dd39cf1667e378b25a082ca796d495d578c5d3
- https://git.kernel.org/stable/c/d52446b3e735cfdbdc2a58342163803bc2e64249
Other CWE-667 (Improper Locking) vulnerabilities
- CVE-2026-64534 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: check INIT_FAILED before…
- CVE-2026-64232 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: block: recompute nr_integrity_segments in…
- CVE-2026-64068 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: netfs: Fix missing locking around retry adding new…
- CVE-2026-64067 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: netfs: Fix missing barriers when accessing…
- CVE-2026-53049 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: gfs2: add some missing log locking Function…
- CVE-2025-22077 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: Revert "smb: client: fix TCP timers deadlock after…