Answer in brief
CVE-2026-68389 records a Unknown severity vulnerability in Bluetooth: hci_qca: Clear memdump state on invalid dump size. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a || >=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <069258d5111eed9ac9586bee42d03d38e2975715 || >=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <cefb44c367b2b52e50f97bc8526d39df9bcf5e60 || >=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <2363a757694752426fc47f3eadde15cf5f791fa5 || >=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <bf587a10c33e5571a299742e45bc18960b9912e7 | 5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a, 069258d5111eed9ac9586bee42d03d38e2975715, cefb44c367b2b52e50f97bc8526d39df9bcf5e60, 2363a757694752426fc47f3eadde15cf5f791fa5, bf587a10c33e5571a299742e45bc18960b9912e7 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68389 records a Unknown severity vulnerability in Bluetooth: hci_qca: Clear memdump state on invalid dump size. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a || >=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <069258d5111eed9ac9586bee42d03d38e2975715 || >=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <cefb44c367b2b52e50f97bc8526d39df9bcf5e60 || >=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <2363a757694752426fc47f3eadde15cf5f791fa5 || >=06d3fdfcdf5cefb06f2024b9d3dad356779399cf <bf587a10c33e5571a299742e45bc18960b9912e7 | 5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a, 069258d5111eed9ac9586bee42d03d38e2975715, cefb44c367b2b52e50f97bc8526d39df9bcf5e60, 2363a757694752426fc47f3eadde15cf5f791fa5, bf587a10c33e5571a299742e45bc18960b9912e7 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.