# CVE-2026-10641: Out-of-bounds write in Bluetooth HFP Hands-Free CIND indicator parsing (cind_handle_values)

> A remote attacker can cause memory corruption and denial of service in Zephyr RTOS by sending a malformed Bluetooth HFP response.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-wx5j-q6f2-59p3

## What is CVE-2026-10641?

CVE-2026-10641 is a high-severity memory corruption vulnerability in Zephyrproject Zephyr, published on 17 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Zephyr's Bluetooth Classic Hands-Free Profile (HFP) Hands-Free role parser (subsys/bluetooth/host/classic/hfp_hf.c) contains an out-of-bounds write. During Service Level Connection setup the HF sends AT+CIND=? and parses the AG's +CIND: response in cind_handle(), which assigns a per-entry counter index and calls cind_handle_values() for each list element. cind_handle_values() then wrote hf->ind_table[index] = i without verifying that index is within the 20-element int8_t ind_table[] array of struct bt_hfp_hf. Because the parser places no cap on the number of +CIND: list entries, a remote Attendant Gateway (a malicious, compromised, or spoofed peer the device connects to over Bluetooth) can send a response with more than 20 recognized indicator entries and drive index arbitrarily large, writing a small attacker-positioned value past the array into adjacent struct fields (feature masks, SDP/version state, the calls[] array, work/atomic bookkeeping) and potentially beyond the static connection pool slot. This yields memory corruption and at least denial of service of the Bluetooth host, triggered by a single malformed AT response with no user interaction. The sibling consumer ag_indicator_handle_values() already performed the equivalent bounds check; this commit adds the same index >= ARRAY_SIZE(hf->ind_table) guard to close the gap. Affects builds with CONFIG_BT_HFP_HF enabled; introduced with the original HFP HF CIND parser (~v1.7) and present through v4.4.0.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-10641?

It affects 1 product.


Products: Zephyrproject Zephyr.

## How do I fix CVE-2026-10641?

No fix has been published for CVE-2026-10641 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10641 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10641 exists.

## Other vulnerabilities in Zephyrproject Zephyr

- [CVE-2026-5067](https://insights.sbomify.com/CVE-2026-5067/): Out-of-bounds read/write in HTTP WebSocket upgrade via non-null-terminated Sec-WebSocket-Key (critical 9.8)
- [CVE-2022-3806](https://insights.sbomify.com/CVE-2022-3806/): Bluetooth HCI Error Handling Double Free (critical 9.8)
- [CVE-2017-14199](https://insights.sbomify.com/CVE-2017-14199/): Memory corruption in getaddrinfo (critical 9.8)
- [CVE-2018-1000800](https://insights.sbomify.com/CVE-2018-1000800/): Null dereference in n/a (critical 9.8)
- [CVE-2021-3329](https://insights.sbomify.com/CVE-2021-3329/): DOS: Incorrect handling of the initial HCI ACL_MTU handshake packet leads to crash of bluetooth host layer (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10641 and fix it if it is affected.

What it is: CVE-2026-10641 is a high-severity memory corruption vulnerability in Zephyrproject Zephyr, published on 17 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10641 exists.

Affected product: Zephyrproject Zephyr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10641/ (Markdown: https://insights.sbomify.com/CVE-2026-10641/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10641
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10641
- OSV: https://osv.dev/vulnerability/CVE-2026-10641

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10641/
Summaries are generated and may contain mistakes; the official description above is the record.