LOW CVSS 3.1
Published: 2026-06-30

CVE-2026-10654

zephyrproject zephyr Security Advisory (CVE-2026-10654)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2026-10654?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2026-10654 impacting zephyrproject zephyr. Evaluated with CVSS Base Score of 3.1 (LOW).

Original NVD Description

Source: NIST NVD
A race condition in the Zephyr Bluetooth Classic RFCOMM host stack (subsys/bluetooth/host/classic/rfcomm.c) mishandles a simultaneous bidirectional session disconnect. When the local device has initiated a session teardown (state BT_RFCOMM_STATE_DISCONNECTING, DISC sent, RTX timer armed) and the connected peer concurrently sends its own DISC frame for dlci 0, rfcomm_handle_disc() invokes rfcomm_session_disconnected(), which unconditionally forced the session to BT_RFCOMM_STATE_DISCONNECTED without ever calling bt_l2cap_chan_disconnect(). Because the recovery timer was also cancelled and a later UA is ignored in the DISCONNECTED state, the session becomes permanently wedged: the underlying L2CAP channel is never released and the session slot in the fixed bt_rfcomm_pool[CONFIG_BT_MAX_CONN] array is never reclaimed (its conn pointer stays set). Subsequent bt_rfcomm_dlc_connect() calls on that connection fail with -EINVAL due to the invalid session state, so RFCOMM service is denied for that peer, and repeated occurrences can exhaust the session pool. The DISC frame is peer-controlled over the air, but exploitation requires the peer's DISC to collide with a local-initiated disconnect (a high-complexity timing race). Impact is availability/resource-leak only; there is no memory-safety, confidentiality, or integrity consequence. The defect shipped in released versions (present in v4.4.0 and earlier). The fix only transitions to DISCONNECTED when the session is not already in DISCONNECTING, preserving the proper L2CAP teardown path.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Adjacent (AV:A)
Requires shared subnet / local network access
Attack Complexity
High (AC:H)
Depends on race conditions or environment
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
None (C:N)
No data confidentiality impact
Integrity
None (I:N)
No system modification impact
Availability
Low (A:L)
Partial service performance degradation

🎯 Affected Versions Matrix

Affected Product zephyrproject / zephyr
Affected Versions *
Weakness Enumeration CWE-362

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2026-10654 impacting zephyrproject zephyr.

⚡ Nuclei Detection Template (YAML) cve-2026-10654.yaml
id: cve-2026-10654

info:
  name: zephyrproject zephyr - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: low
  description: |
    Automated signature & scanner for CVE-2026-10654 affecting zephyrproject zephyr.
    Evaluation: A race condition in the Zephyr Bluetooth Classic RFCOMM host stack (subsys/bluetooth/host/classic/rfcomm.c) mishandles a simultaneous bidirectional se...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2026-10654
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
    cvss-score: 3.1
    cve-id: CVE-2026-10654
    cwe-id: CWE-362
  tags: cve,cve-2026-10654,zephyrproject,zephyr,low

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "zephyr"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2026-10654.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2026-10654
# Target: zephyrproject zephyr | CVSS: 3.1 (LOW)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2026-10654 (zephyrproject zephyr)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against zephyrproject zephyr scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2026-10654.sh
# Recommended Remediation & Patching Commands for CVE-2026-10654
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install zephyr 2>/dev/null || \
sudo dnf upgrade zephyr 2>/dev/null || \
sudo yum update zephyr

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i zephyr 2>/dev/null || rpm -qa | grep -i zephyr

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2026-10654 in zephyrproject zephyr?

Review vendor-specific security notices and update zephyrproject zephyr packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2026-10654?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2026-10654?

CVE-2026-10654 is classified with a CVSS 3.1 Base Score of 3.1 (LOW). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
3.1
LOW SEVERITY
CVE ID CVE-2026-10654
Weakness CWE-362
Vendor zephyrproject
Product zephyr
Published 2026-06-30
Vector CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L