Skip to main content

Linux Kernel EUVDEUVD-2026-55577

| CVE-2026-68391 HIGH
2026-08-10 Linux GHSA-r93r-qrfp-h69j
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.8 HIGH

Local attack via Bluetooth management socket requires low privileges; UAF enables arbitrary kernel read/write with full C/I/A impact; scope unchanged as kernel compromise stays within the host.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
5.3 HIGH
AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Red Hat
7.0 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 - 02:49 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.8 (HIGH)
CVE Published
Aug 10, 2026 - 12:04 cve.org
HIGH 7.8
CVE Published
Aug 10, 2026 - 12:04 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

Bluetooth: mgmt: hold reference for hci_conn in mgmt_pending_cmds

Dereferencing RCU-protected pointers outside critical sections is invalid and may lead to UAF. Use of hci_conn in hci_sync callbacks also needs to hold refcount to avoid UAF.

Take appropriate locks for hci_conn lookups, and take refcount for hci_conn pointers stored in mgmt_pending_cmd so that the pointer stays valid.

When accessing conn->state, ensure hdev->lock is held to avoid data race.

AnalysisAI

Use-after-free and data race conditions in the Linux kernel Bluetooth management subsystem allow a local low-privileged attacker to corrupt kernel memory, potentially escalating privileges to root. Affected kernels fail to properly hold reference counts on hci_conn objects stored in mgmt_pending_cmd structures and fail to acquire hdev->lock before accessing conn->state, enabling RCU-protected pointers to be dereferenced after the underlying memory has been freed. No public exploit or CISA KEV listing has been identified at time of analysis; EPSS of 0.17% (6th percentile) reflects low observed exploitation pressure despite the high CVSS score.

Technical ContextAI

The vulnerability resides in the Linux kernel Bluetooth management (mgmt) subsystem, specifically in how hci_conn objects are tracked within mgmt_pending_cmd structures and used inside hci_sync callbacks. RCU (Read-Copy-Update) is a Linux kernel synchronization primitive that permits lock-free reads under a critical section guard; dereferencing RCU-protected pointers outside these critical sections is unsafe because the memory can be reclaimed concurrently. The bug has two related facets: first, hci_conn pointers stored in mgmt_pending_cmd are not reference-counted, so the hci_conn object can be freed while the pending command still holds a raw pointer; second, hci_conn objects used in hci_sync callbacks similarly lack refcount protection, creating a parallel UAF window. Separately, accesses to conn->state are performed without holding hdev->lock, constituting a classic TOCTOU data race. CPE data identifies the affected product as cpe:2.3:a:linux:linux (Linux kernel), with the vulnerable code introduced at commit 7b445e220db9a2c58be5d09bbbd322abf1b1452a and spanning multiple stable series from Linux 6.0 onward. No formal CWE is assigned in the input, but the root cause class is clearly CWE-416 (Use After Free) compounded by CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization).

RemediationAI

Update the Linux kernel to a fixed stable release: 6.6.148, 6.12.101, or 7.1.6 for the respective stable series, or 7.2-rc4 or later for development builds. Fixes are confirmed in upstream commits at https://git.kernel.org/stable/c/b56f2ecafc08f372bf0529f9c4f3f429cb1702bc and related backport commits. Distribution-specific kernels (RHEL, Ubuntu, Debian, SUSE) should be updated as their respective advisories are issued. As a compensating control where patching is not immediately possible, disabling Bluetooth kernel modules (rmmod btusb bluetooth; blacklist them in /etc/modprobe.d/) will eliminate the attack surface entirely at the cost of losing all Bluetooth functionality on the host. Restricting local user access to Bluetooth management sockets via capability controls (CAP_NET_ADMIN) using tools such as seccomp profiles or AppArmor policy reduces risk in multi-tenant environments, though it does not eliminate the vulnerability for privileged processes. The NVD advisory is at https://nvd.nist.gov/vuln/detail/CVE-2026-68391.

Vendor StatusVendor

SUSE

Severity: Important
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-55577 vulnerability details – vuln.today

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