CVE-2026-68389
HighCVSS 8.8Exploitation Probability (EPSS)
Low risk17th percentile - higher than 17% of all known CVEs
Summary
In the Linux kernel, the Bluetooth hci_qca driver has a use-after-free vulnerability when handling an invalid dump size from the controller. When the controller reports a zero dump size, the error path frees the local object but does not clear the pointer in the qca structure, leading to later access to freed memory.
Risk Assessment
An attacker could cause a system crash or potentially execute code in kernel context, posing a serious threat to system integrity and availability.
Recommendation
Apply a Linux kernel update containing the fix that clears the pointer and memdump state before returning from the error path.
Original NVD description (English source)
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.