BT: Invalid channel map in CONNECT_IND results to Deadlock

published 2022-06-28 4y ago modified 2026-06-17 4mo ago also EUVD-2021-26759

cvss: 4.0; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 11%
public exploits: 0; none known

Invalid channel map in CONNECT_IND results to Deadlock. Zephyr versions >= v2.5.0 Improper Check or Handling of Exceptional Conditions (CWE-703). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-3c2f-w4v6-qxrp

Patch / fix

fixed in 1

zephyrproject zephyr 2.6.0

Is CVE-2021-3433 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.0	CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD	3.1	3.3	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:N/I:N/A:P

Affected products

zephyrproject-rtos zephyr

Classification

Weakness

CWE-703 Improper Check or Handling of Exceptional Conditions

References

github.com /zephyrproject-rtos/zephyr/security/advisories/GHSA-3c2f-w4v6-qxrp
vendor-advisory

Sources

CVE List CVE-2021-3433
NVD CVE-2021-3433

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.