Skip to main content

Linux Kernel CVE-2026-68389

| EUVDEUVD-2026-55575 HIGH
2026-08-10 Linux GHSA-ghf3-w254-j47x
8.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

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

AC:H because triggering a zero-size QCA dump requires non-standard controller interaction beyond routine Bluetooth range exploitation; other metrics match the official vector.

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

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

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

Lifecycle Timeline

5
Analysis Generated
Aug 14, 2026 - 02:52 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
8.8 (HIGH)
Patch available
Aug 10, 2026 - 14:18 EUVD
CVE Published
Aug 10, 2026 - 12:04 cve.org
HIGH 8.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: hci_qca: Clear memdump state on invalid dump size

qca_controller_memdump() allocates qca->qca_memdump before processing the first dump packet. For a sequence-zero packet it then disables IBS, marks memdump collection active, and reads the advertised dump size.

If the controller reports a zero dump size, the error path frees the local qca_memdump object and returns without clearing qca->qca_memdump or undoing the collection state. A later memdump work item initializes its local pointer from qca->qca_memdump and skips allocation when that pointer is non-NULL, so it can operate on freed memory. The stale collection and IBS-disabled flags can also leave waiters or later transmit handling blocked behind an aborted dump.

Clear the saved pointer and memdump state before returning from the invalid-size path, matching the cleanup used when hci_devcd_init() fails.

A static analysis checker reported the stale memdump state, and manual source review confirmed the invalid-size failure path.

AnalysisAI

Use-after-free in the Linux kernel Bluetooth hci_qca driver allows an attacker within Bluetooth radio range to corrupt kernel heap memory by inducing a Qualcomm Atheros QCA controller to report a zero-length memory dump. Systems running unpatched kernels prior to 6.6.148, 6.12.101, 6.18.42, or 7.1.6 with QCA Bluetooth hardware are exposed, with potential impact spanning kernel information disclosure, memory corruption, and denial of service. No public exploit code has been identified at time of analysis, and EPSS probability is very low at 0.17% (6th percentile), indicating no evidence of active or widespread exploitation.

Technical ContextAI

The vulnerable function qca_controller_memdump() in drivers/bluetooth/hci_qca.c processes memory dump packets transmitted by Qualcomm Atheros Bluetooth controllers (CPE: cpe:2.3:a:linux:linux:*). On receipt of a sequence-zero dump packet, the driver disables IBS (in-band sleep), marks collection active, and reads the advertised dump size from the controller-supplied data. When the controller reports zero as the dump size, an error path frees the locally-allocated qca_memdump object but critically omits clearing the shared qca->qca_memdump pointer and reverting the collection and IBS-disabled state flags - an incomplete cleanup analogous to CWE-459. A subsequently scheduled memdump work item reads the non-NULL stale pointer, bypasses re-allocation entirely, and dereferences freed heap memory - a textbook use-after-free (CWE-416). Concurrently, the lingering IBS-disabled and dump-active flags can permanently block Bluetooth transmit paths and indefinitely stall waiting threads, contributing to the availability impact. The root cause was identified via static analysis and confirmed by manual source review per the kernel commit message.

RemediationAI

The primary fix is upgrading to a patched stable kernel release: 6.6.148 or later for the 6.6 LTS branch, 6.12.101 or later for the 6.12 branch, 6.18.42 or later for the 6.18 branch, or 7.1.6 or later for the 7.1 branch. All patch commits are available at the kernel stable tree links cited in the affected products section. Distribution-packaged kernels (Debian, Ubuntu, RHEL, Fedora, etc.) should receive these fixes through standard security update channels - apply pending kernel updates and reboot to activate. For systems where immediate kernel upgrade is not feasible, disabling Bluetooth entirely via rfkill block bluetooth eliminates the attack surface with no security downside, at the cost of Bluetooth functionality. Alternatively, blacklisting the hci_qca module by adding blacklist hci_qca to /etc/modprobe.d/blacklist.conf and rebooting prevents the driver from loading, though this disables QCA Bluetooth hardware completely. Restricting Bluetooth to paired, trusted devices via platform policy reduces opportunistic exposure but does not prevent exploitation by a sufficiently motivated attacker who can spoof or compromise a trusted device identity.

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

CVE-2026-68389 vulnerability details – vuln.today

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