CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-10641 remediation guide

zephyrproject zephyr

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 At...

Open CVE record
Productzephyrproject zephyr
Affected versions>= 1.7.0 < 4.5.0, >= 3.7.0 < 3.7.3, >= 4.0.0 < 4.3.1, >= 4.4.0 < 4.4.2
Fixed versions3.7.3, 4.3.1, 4.4.2
Priority basisReview · CVSS 7.1 · EPSS 0.28%
01

Identify the affected asset

Confirm whether zephyrproject zephyr is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 1.7.0 < 4.5.0, >= 3.7.0 < 3.7.3, >= 4.0.0 < 4.3.1, >= 4.4.0 < 4.4.2. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 3.7.3, 4.3.1, 4.4.2. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.