Skip to main content

Linux Kernel EUVDEUVD-2026-55290

| CVE-2026-68189 HIGH
2026-08-10 Linux GHSA-jprq-4ghp-p3f9
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

Race condition requires precise timing between concurrent kernel paths, justifying AC:H over NVD's AC:L; PR:L reflects required HCI management socket access.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Analysis Generated
Aug 14, 2026 - 03:39 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.8 (HIGH)
CVE Published
Aug 10, 2026 - 12:00 cve.org
HIGH 7.8
CVE Published
Aug 10, 2026 - 12:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: hci_sync: Protect UUID list traversal

The hci_sync conversion moved class-of-device and EIR generation from an HCI request built under hdev->lock to asynchronous command sync work. The worker holds hdev->req_lock, but that lock does not serialize access to hdev->uuids against add_uuid() and remove_uuid(), which update the list under hdev->lock.

The following interleaving can therefore occur:

CPU0 (command sync work) CPU1 (management socket) fetch uuid from the list list_del(&uuid->list) kfree(uuid) read uuid->size

KASAN reports the resulting use-after-free:

BUG: KASAN: slab-use-after-free in eir_create+0xb8f/0xee0 Read of size 1 at addr ffff88810dbd8620 by task kworker/u17:0/87 Workqueue: hci0 hci_cmd_sync_work Call Trace: eir_create+0xb8f/0xee0 hci_update_eir_sync+0x1c0/0x330 hci_cmd_sync_work+0x13c/0x290 process_one_work+0x63a/0x1070 worker_thread+0x45b/0xd10

Allocated by task 86: __kasan_kmalloc+0x8f/0xa0 add_uuid+0x18a/0x4b0 hci_sock_sendmsg+0x1033/0x1ea0

Freed by task 92: __kasan_slab_free+0x43/0x70 kfree+0x131/0x3c0 remove_uuid+0x25e/0x560 hci_sock_sendmsg+0x1033/0x1ea0

Hold hdev->lock while generating and committing the class-of-device and EIR snapshots. Release it before sending an HCI command, so controller waits do not happen under the device lock. This protects all UUID list walks in these paths and restores the serialization lost in the command sync conversion.

AnalysisAI

Use-after-free in the Linux kernel Bluetooth HCI sync subsystem allows a local low-privileged attacker to corrupt kernel memory, with potential for privilege escalation and full system compromise. The flaw is a race condition between the hci_sync async command work (holding hdev->req_lock) and Bluetooth management socket operations (add_uuid/remove_uuid, which operate under hdev->lock), enabling concurrent unsafe UUID list access confirmed by KASAN. No public exploit code exists and EPSS is 0.20% (10th percentile), but the high C/I/A CVSS impact reflects the severity of kernel-level memory corruption if the race is won.

Technical ContextAI

The Linux kernel's Bluetooth HCI (Host Controller Interface) subsystem uses an async command sync worker (hci_cmd_sync_work) to generate class-of-device bitmasks and EIR (Extended Inquiry Response) payloads. A prior refactoring (hci_sync conversion, introduced around commit 161510ccf91c961638940b03abb1ee804be53a97, approximately Linux 5.17) moved these operations out of hdev->lock-protected HCI request building into async work that holds only hdev->req_lock. However, hdev->req_lock does not serialize access to hdev->uuids, which is modified by add_uuid() and remove_uuid() under hdev->lock. This lock mismatch creates a classic TOCTOU race condition: the worker fetches a uuid pointer from the list, a concurrent management socket call frees it via kfree(), and the worker then reads from the freed memory in eir_create(). KASAN confirms the slab-use-after-free at eir_create+0xb8f/0xee0. The CWE is not formally tagged but this is CWE-416 (Use After Free) with an underlying CWE-362 (Race Condition) root cause. Affected CPEs: cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*.

RemediationAI

Apply the upstream kernel fix by upgrading to a patched version: Linux 7.1.6, Linux 6.12.101, Linux 6.18.42, or Linux 6.6.148, depending on your deployed stable branch; Linux 7.2-rc5 for development trees. Stable fix commits are available at https://git.kernel.org/stable/c/e4fa2c5c261d736b8e58759fdef3a968d510630c, https://git.kernel.org/stable/c/a351f68fb24828b23a971e00b8238ee0e8a40380, https://git.kernel.org/stable/c/a42f5536ea9c00e13f0c0fbb330feed95e2365ca, https://git.kernel.org/stable/c/fe13adc258df88d95789e5673c7ba5178b5f8b28, and https://git.kernel.org/stable/c/e9027ffbf5a0f3c12ca8900822e884eae9f0821b. If immediate kernel upgrade is not feasible, a compensating control is to disable Bluetooth entirely on systems where it is not operationally required (modprobe -r bluetooth or blacklisting the module); this eliminates the hci_sync code path entirely with no side effects beyond loss of Bluetooth functionality. Restricting unprivileged access to HCI management sockets via udev rules or seccomp/AppArmor/SELinux policies reduces exposure on systems that require Bluetooth but do not grant all local users management access.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

EUVD-2026-55290 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy