# Bluetooth: hci_qca: Clear memdump state on invalid dump size

CVE record · `CVE-2026-68389`

- **Identifiers:** `CVE-2026-68389`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 10 Aug 2026, 12:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `06d3fdfcdf5cefb06f2024b9d3dad356779399cf to before 5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a` (git)
  - affected: `06d3fdfcdf5cefb06f2024b9d3dad356779399cf to before 069258d5111eed9ac9586bee42d03d38e2975715` (git)
  - affected: `06d3fdfcdf5cefb06f2024b9d3dad356779399cf to before cefb44c367b2b52e50f97bc8526d39df9bcf5e60` (git)
  - affected: `06d3fdfcdf5cefb06f2024b9d3dad356779399cf to before 2363a757694752426fc47f3eadde15cf5f791fa5` (git)
  - affected: `06d3fdfcdf5cefb06f2024b9d3dad356779399cf to before bf587a10c33e5571a299742e45bc18960b9912e7` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.6`
  - unaffected: `before 6.6` (semver)
  - unaffected: `6.6.148 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.101 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.42 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.6 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0025, the 17th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 10 Aug 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-68389](https://www.cve.org/CVERecord?id=CVE-2026-68389)
- [NVD: CVE-2026-68389](https://nvd.nist.gov/vuln/detail/CVE-2026-68389)

### References from the CNA

- <https://git.kernel.org/stable/c/5a3945e8dea6c9a8ec9e981169ac9487e1d6ad6a>
- <https://git.kernel.org/stable/c/069258d5111eed9ac9586bee42d03d38e2975715>
- <https://git.kernel.org/stable/c/cefb44c367b2b52e50f97bc8526d39df9bcf5e60>
- <https://git.kernel.org/stable/c/2363a757694752426fc47f3eadde15cf5f791fa5>
- <https://git.kernel.org/stable/c/bf587a10c33e5571a299742e45bc18960b9912e7>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-68389>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-68389/>. Everything for agents: <https://agentprime.io/llms.txt>.
