Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-93666Published 2026-11-16

CVE-2026-93666 — zephyrproject zephyr

medium

As of 2026-11-17, CVE-2026-93666 is a MEDIUM-severity vulnerability in zephyrproject zephyr, CVSS v3.1 5.3, EPSS 0.1% (2.4th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-93666 as of 2026-11-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
5.3/10Medium
EPSS
0.1%Higher than 2.4% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
2.7/10Threadlinqs triage score
Published
Updated 2026-11-17
CVSS v3.1 5.3 (MEDIUM) · EPSS 0.1% (higher than 2.4% of all scored CVEs) · Priority 2.7/10 · Published 2026-11-16

Last updated:

What is CVE-2026-93666?

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.

The record classifies CVE-2026-93666 under weakness class CWE-833. Its CVSS v3 base vector states that the flaw is reachable from an adjacent network, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 3 days ago.

Severity and exploitation probability

CVSS v3.1 base score
5.3 — MEDIUM
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 2.4% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
2.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-11-16

Is CVE-2026-93666 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-93666

Patch reference: https://github.com/zephyrproject-rtos/zephyr/commit/c43dcb26565b648fd9441c2c9ff88e1ce32cbb10. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-93666

No threat campaign in the Threadlinqs corpus currently references CVE-2026-93666, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references