Vulnerability · Published Aug 10, 2026 · Assigned by Linux

CVE-2026-68389Bluetooth: hci_qca: Clear memdump state on invalid dump size

High 8.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 17% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)8.8High
Exploit odds (30 days)0.3%top 83.0% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.101-1DEBIAN-CVE-2026-68389
Debian:14linux7.1.6-1DEBIAN-CVE-2026-68389
Debian:12linux-6.126.12.101-1~deb12u1DEBIAN-CVE-2026-68389
Ubuntu:24.04:LTSlinux6.8.0-147.147UBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux7.0.0-38.38UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-aws6.8.0-1067.70UBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-aws7.0.0-1014.14UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure6.8.0-1071.79UBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-azure7.0.0-1017.17UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1017.17~24.04.1UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1069.76UBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1016.16UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-gcp6.8.0-1071.79UBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-gcp7.0.0-1014.14UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-gke6.8.0-1066.74UBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-gke7.0.0-1008.9UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1052.56UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-38.38~24.04.4UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-ibm6.8.0-1067.68UBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-ibm7.0.0-1015.15UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-147.147.1UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1024.25~24.04.1UBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2022.23UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1036.39UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1015.15UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-oracle6.8.0-1064.67UBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-oracle7.0.0-1013.13UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-realtime7.0.0-38.38.1UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-68389
Ubuntu:26.04:LTSlinux-riscv7.0.0-38.38.1UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-38.38.1~24.04.1UBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-68389
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-vmware6.8.0-1008.8UBUNTU-CVE-2026-68389
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-68389

Affected products (as reported)

VendorProductVersions
Linux Linux 06d3fdfcdf5cefb06f2024b9d3dad356779399cf – before 5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a06d3fdfcdf5cefb06f2024b9d3dad356779399cf – before 069258d5111eed9ac9586bee42d03d38e297571506d3fdfcdf5cefb06f2024b9d3dad356779399cf – before cefb44c367b2b52e50f97bc8526d39df9bcf5e6006d3fdfcdf5cefb06f2024b9d3dad356779399cf – before 2363a757694752426fc47f3eadde15cf5f791fa506d3fdfcdf5cefb06f2024b9d3dad356779399cf – before bf587a10c33e5571a299742e45bc18960b9912e7
Linux Linux 6.6

References