CVE-2026-10654 zephyrproject CVE debrief

Who should care

Defenders responsible for Zephyr Bluetooth Classic deployments should assess exposure and apply the patch. This includes operators, platform administrators, vulnerability management teams, and security teams who need to evaluate the impact of this vulnerability on their systems and take appropriate actions.

Why it matters

A race condition in the Zephyr Bluetooth Classic RFCOMM host stack could lead to a denial of further RFCOMM service, potentially impacting Zephyr deployments.

• Denial of further RFCOMM service
• Potential exhaustion of the session pool

Technical summary

A race condition in the Zephyr Bluetooth Classic RFCOMM host stack (subsys/bluetooth/host/classic/rfcomm.c) mishandles a simultaneous bidirectional session disconnect, potentially leading to a denial of further RFCOMM service. This vulnerability affects Zephyr Bluetooth Classic deployments. The issue arises from a flawed handling of session disconnections, which can lead to a denial of service and potential exhaustion of the session pool. Defenders should review and apply patches, verify affected versions, and assess exposure.

Defensive priority

Medium

Recommended defensive actions

• Review and apply the patch referenced in the source item
• Verify the affected versions of Zephyr and assess exposure
• Monitor for potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, but limited information is available on potential exploitation or impact. Defenders should verify the affected versions of Zephyr and assess exposure. The CVE Program record and NIST NVD detail page offer official vulnerability assessments. A patch is referenced in the source item, which should be reviewed and applied. Evidence limits and unknown affected scope should be considered when evaluating this vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.