CVE-2026-93666
Awaiting Analysis Awaiting Analysis - Queue

Denial of Service in Zephyr Bluetooth SDP Client

Vulnerability report for CVE-2026-93666, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-16

Last updated on: 2026-11-16

Assigner: Zephyr Project

Description

The Bluetooth Classic SDP client built its outgoing request PDUs with bt_sdp_create_pdu(), which allocates from the sdp_pool net-buf pool with a K_FOREVER timeout and no failure handling, in sdp_client_ss_search(), sdp_client_sa_search() and sdp_client_ssa_search() in subsys/bluetooth/host/classic/sdp.c. All of these run on the Bluetooth workqueue bt_workq (via sdp_client_work_handler(), the L2CAP sdp_client_connected() callback, or the continuation-state follow-up from a received response), which is the same single thread that dispatches incoming HCI ACL and event traffic, drives L2CAP, and performs connection and channel teardown. sdp_pool holds only CONFIG_BT_MAX_CONN buffers (one by default) and is shared with the SDP server role. An unauthenticated peer within BR/EDR range can drive both halves of the trigger. The SDP L2CAP server is registered at BT_SECURITY_L0, so any inbound SDP request makes the device allocate the pool's buffer for a response, which is held until the controller has transmitted it. The same peer can then cause a client request to be issued while the pool is empty: in-tree profiles start SDP discovery from inbound connection callbacks (for example hfp_hf_accept() calls bt_sdp_discover() through hfp_hf_create(), and hfp_ag.c mirrors this), and a peer acting as an SDP server can force repeated client requests by answering with partial responses carrying continuation state. With the pool empty, the allocation blocks uninterruptibly and freezes the entire Bluetooth host. The stall becomes permanent when the release of the outstanding buffer itself depends on the blocked workqueue: if the link carrying the queued PDU is dropped or stalls, hci_disconn_complete() and the L2CAP channel cleanup that purges the channel TX queue are themselves bt_workq work items, so the buffer is never returned. The result is an unrecoverable denial of service of all Bluetooth functionality until reboot; there is no memory-safety, confidentiality or integrity impact. The fix allocates client PDUs with K_NO_WAIT via a new sdp_client_create_pdu(), propagates -ENOBUFS, parks the session on a new SDP_CLIENT_FLAG_WAIT_FOR_TX_BUF flag, and adds an sdp_pool destructor that re-submits the SDP client worker when a buffer becomes available. Note that the SDP server role still allocated from the same pool with K_FOREVER at this commit; that path was addressed separately.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-16
Last Modified
2026-11-16
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
zephyrproject zephyr From 1.7.0 (inc) to 4.5.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-833 The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Bluetooth Classic denial of service issue. An unauthenticated attacker within Bluetooth range can exploit it by sending crafted requests that exhaust a shared memory pool used for SDP (Service Discovery Protocol) operations. The system allocates memory with no timeout and no failure handling, causing the Bluetooth host to freeze permanently if the memory pool is exhausted. This disrupts all Bluetooth functionality until a reboot.

Detection Guidance

This vulnerability may cause a complete freeze of Bluetooth functionality on affected systems. Detection involves monitoring for unresponsive Bluetooth services or system hangs during Bluetooth operations. Check Bluetooth logs for stalled SDP requests or pool allocation failures. No specific commands are provided in the context.

Impact Analysis

If you use a device with this vulnerability, an attacker within Bluetooth range could cause your device to stop responding to Bluetooth requests. This means you may lose connectivity for Bluetooth devices like headphones, keyboards, or file transfers. The only recovery is rebooting the device, as the issue is unrecoverable without intervention.

Mitigation Strategies

Apply the vendor-provided patch that replaces K_FOREVER with K_NO_WAIT for SDP PDU allocations and introduces buffer management improvements. Monitor for buffer exhaustion conditions and ensure Bluetooth workqueue tasks are not blocked indefinitely.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-93666. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...