CVE-2026-93668Hinoki check available

Bluetooth hang via blocking SDP response allocation

Published Nov 16, 2026 · Updated Nov 16, 2026

Deadlock in Zephyr RTOS 1.6.0 through 4.4.2 allows remote attackers to hang the Bluetooth host via unauthenticated Bluetooth SDP requests. In subsys/bluetooth/host/classic/sdp.c, bt_sdp_recv() allocates responses from a fixed shared pool with K_FOREVER, blocking receive processing when pipelined requests exhaust buffers and the peer withholds acknowledgements. Exploitation requires a connectable BR/EDR device within radio range and no pairing; all Bluetooth connections stall, generally until reset, although 3.7.0 through 4.1.x recover at link supervision timeout and remain susceptible to repeated stalls.

CVSS severity6.5
Medium
EPSS probability0.14%
Next 30 days · Nov 22, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Contact us

Summary

What happened

Deadlock in Zephyr RTOS 1.6.0 through 4.4.2 allows remote attackers to hang the Bluetooth host via unauthenticated Bluetooth SDP requests. In subsys/bluetooth/host/classic/sdp.c, bt_sdp_recv() allocates responses from a fixed shared pool with K_FOREVER, blocking receive processing when pipelined requests exhaust buffers and the peer withholds acknowledgements. Exploitation requires a connectable BR/EDR device within radio range and no pairing; all Bluetooth connections stall, generally until reset, although 3.7.0 through 4.1.x recover at link supervision timeout and remain susceptible to repeated stalls.

The record

CVE
CVE-2026-93668
Published
Nov 16, 2026
Updated
Nov 16, 2026
Vendor
Zephyr Project
Product
Zephyr RTOS
Classifications
CWE-833, T1499.004
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Nov 16, 2026CVE publishedPublication date reported by the CVE source.
  2. Nov 16, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1.6.0 <4.5.0

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Zephyr Project · Zephyr RTOSversion=1.6.0 <4.5.0

Published CVSS scores

6.5Zephyr ProjectCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-833Deadlock
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Contact us