LiveActive security incident?Get immediate response
CVE Record

CVE-2023-1901: HCI send_sync Dangling Semaphore Reference Re-use

The bluetooth HCI host layer logic not clearing a global reference to a semaphore after synchronously sending HCI commands may allow a malicious HCI Controller to cause the use of a dangling reference in the host layer, leading to a crash (DoS) or potential RCE on the Host layer.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-1901 affects Zephyr’s Bluetooth HCI host logic. A malicious or compromised HCI controller may be able to crash the host, and the source notes potential code execution. Business urgency is highest for products where Bluetooth controllers, firmware, or attached HCI hardware are untrusted or field-updatable.

Executive priority

Treat as a moderate operational risk. Prioritize embedded products with Bluetooth enabled, especially where controller firmware can be changed outside normal trust controls. Lack of confirmed exploitation lowers urgency, but potential host crash and possible RCE justify timely verification and patch planning.

Technical view

The flaw is a dangling semaphore reference re-use issue in Zephyr’s Bluetooth HCI host layer. The host does not clear a global semaphore reference after synchronous HCI command handling. A malicious HCI controller may trigger use of that stale reference, causing denial of service or potential host-layer RCE.

Likely exposure

Exposure is likely limited to products using Zephyr with the affected Bluetooth HCI host-layer behavior. The supplied bundle names Zephyr but does not provide precise vulnerable or fixed release ranges, so teams must verify against the Zephyr advisory and their SBOMs.

Exploitation context

The CVSS vector indicates adjacent attack vector, high complexity, low privileges, and no user interaction. The provided KEV flag is false, and no supplied source states active exploitation. Practical risk depends on whether an attacker can influence or replace the HCI controller path.

Researcher notes

The supplied evidence is enough to characterize the bug class and attack preconditions, but not enough to name fixed versions or exploit maturity beyond KEV=false. Validate exposure through Zephyr advisory details, build configuration, and product-specific HCI controller trust boundaries.

Mitigation direction

  • Check the Zephyr GitHub advisory for affected and fixed release details.
  • Update Zephyr to the vendor-recommended fixed version when confirmed.
  • Restrict use of untrusted or field-replaceable Bluetooth HCI controllers.
  • Disable Bluetooth functionality where it is unnecessary or cannot be remediated.
  • Monitor vendor guidance for backports or product-specific mitigations.

Validation and detection

  • Inventory products using Zephyr with Bluetooth HCI host support enabled.
  • Map firmware and SBOM data to the Zephyr advisory’s affected range.
  • Review crash, reset, and Bluetooth controller error logs for anomalies.
  • Confirm whether deployed HCI controllers are trusted, signed, and update-controlled.
  • Run regression testing after applying the vendor-supported Zephyr update.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-672: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-1901 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H1.24.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-1901Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
zephyrproject-rtosZephyrZephyr, *unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-672 · source CWE mapping

Operation on a Resource after Expiration or Release

Operation on a Resource after Expiration or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.