Linux Kernel up to 6.12.95/6.18.38/7.1.3/7.2-rc2 Bluetooth hci_uart_close race condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$0-$5k1.06

Summaryinfo

A vulnerability marked as very critical has been reported in Linux Kernel up to 6.12.95/6.18.38/7.1.3/7.2-rc2. This affects the function hci_uart_close of the component Bluetooth. This manipulation causes race condition. This vulnerability appears as CVE-2026-68085. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability classified as very critical was found in Linux Kernel up to 6.12.95/6.18.38/7.1.3/7.2-rc2. Affected by this vulnerability is the function hci_uart_close of the component Bluetooth. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-68085 since 07/30/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/10/2026).

Upgrading to version 6.12.96, 6.18.39, 7.1.4 or 7.2-rc3 eliminates this vulnerability. Applying the patch d52446b3e735cfdbdc2a58342163803bc2e64249/b9dd39cf1667e378b25a082ca796d495d578c5d3/714d861d35d937f23375a4517569b13917bbbe51/1b0d946d6f08bd39211385bc703a440911b41e46 is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.96/6.18.39/7.1.4/7.2-rc3
Patch: d52446b3e735cfdbdc2a58342163803bc2e64249/b9dd39cf1667e378b25a082ca796d495d578c5d3/714d861d35d937f23375a4517569b13917bbbe51/1b0d946d6f08bd39211385bc703a440911b41e46

Timelineinfo

07/30/2026 CVE reserved
08/10/2026 +11 days Advisory disclosed
08/10/2026 +0 days VulDB entry created
08/10/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-68085 (🔒)
GCVE (CVE): GCVE-0-2026-68085
GCVE (VulDB): GCVE-100-387433

Entryinfo

Created: 08/10/2026 14:25
Changes: 08/10/2026 14:25 (59)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!