# Bluetooth: hci_sync: fix leaks when hci_cmd_sync_queue_once fails

CVE record · `CVE-2026-43021`

- **Identifiers:** `CVE-2026-43021`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 May 2026, 14:15 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: `a106e50be74b0896583f4d010a69f9806e4194f4 to before 7fd74178d4b16dcf47179da634ea9d7c02e3608b` (git)
  - affected: `a106e50be74b0896583f4d010a69f9806e4194f4 to before aca377208e7f7322bf4e107cdec6e7d7e8aa7a88` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.19`
  - unaffected: `before 6.19` (semver)
  - unaffected: `6.19.12 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel Bluetooth code (hci_sync) in version 6.19 before 6.19.12 leaks memory and references when a queued command fails. The source gives few details about what an attacker needs. Upgrade to Linux kernel 6.19.12 or later in the 6.19 series, or 7.0 or later.

Written 17 Nov 2026.

## 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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0011, the 1st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 May 2026, 14:15 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-43021)
- 1 May 2026, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43021)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/7fd74178d4b16dcf47179da634ea9d7c02e3608b>
- <https://git.kernel.org/stable/c/aca377208e7f7322bf4e107cdec6e7d7e8aa7a88>

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-43021>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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