Bluetooth: hci_qca: Clear memdump state on invalid dump size
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s Bluetooth hci_qca driver leaves a freed memdump pointer and active collection state behind when a controller reports a zero dump size. A later memdump work item can use the freed memory, while stale state can block waiters or transmit handling. The input does not establish whether an attacker can trigger this remotely, whether authentication is needed, or whether user interaction is required.
Engineers running Linux kernels with the Bluetooth hci_qca driver should check their exposure; affected versions are not specified.