Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-93672Published 2026-11-16

CVE-2026-93672 — zephyrproject zephyr

medium

As of 2026-11-17, CVE-2026-93672 is a MEDIUM-severity vulnerability in zephyrproject zephyr, CVSS v3.1 5.3, EPSS 0.1% (5.1th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-93672 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 5.1% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
2.9/10Threadlinqs triage score
Published
Updated 2026-11-17
CVSS v3.1 5.3 (MEDIUM) · EPSS 0.1% (higher than 5.1% of all scored CVEs) · Priority 2.9/10 · Published 2026-11-16

Last updated:

What is CVE-2026-93672?

bt_att_find_req_by_user_data() in subsys/bluetooth/host/att.c walks every ATT channel attached to a connection and dereferences chan->req->user_data without checking chan->req. An ATT channel with no client request in flight holds chan->req == NULL — that is its normal idle state, set by att_handle_rsp() when a response resolves the transaction and tested by att_req_send_process() to pick a free channel — so the lookup reads through a NULL pointer as soon as it visits an idle channel. Every other chan->req user in the file already guards the pointer. The lookup is reached from the public bt_gatt_cancel() API and, more importantly, from the host itself: bt_gatt_unsubscribe() calls bt_gatt_cancel() while a subscribe CCC write is still outstanding (BT_GATT_SUBSCRIBE_FLAG_WRITE_PENDING), and call_notify_cb_and_maybe_unsubscribe() in subsys/bluetooth/host/gatt.c invokes bt_gatt_unsubscribe() from the RX path whenever an application notify callback returns BT_GATT_ITER_STOP. A malicious or malfunctioning peer can hold the trigger window open by withholding the ATT Write Response to the CCC write and then sending a notification for the subscribed handle. With CONFIG_BT_EATT the traversal is very likely to meet an idle sibling channel, since ATT channels are prepended to the list and a channel opened after the pending request was sent is visited first. The dereference is a read of a small constant offset from address zero, so the impact is availability only: no memory corruption, no attacker-chosen address and no information disclosure. On platforms and configurations where a near-NULL read traps — TrustZone non-secure images, MMU targets, native_sim, or builds with CONFIG_NULL_POINTER_EXCEPTION_DETECTION_MPU/_DWT — the fault occurs in the Bluetooth RX context and results in a fatal error and device reset. On a plain Cortex-M build with the vector table mapped at address 0 and null-pointer detection disabled (the default) the read succeeds and the defect is inert. The fix adds an explicit chan->req != NULL test to the channel traversal and additionally rejects a NULL user_data argument, which would otherwise have matched, and cancelled, an unrelated request.

The record classifies CVE-2026-93672 under weakness class CWE-476. 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 5.1% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
2.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-11-16

Is CVE-2026-93672 being exploited?

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

Affected products and versions

How to fix CVE-2026-93672

Patch reference: https://github.com/zephyrproject-rtos/zephyr/commit/c8e360006acbdffb316b0061f25f230f7ace287c. 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-93672

No threat campaign in the Threadlinqs corpus currently references CVE-2026-93672, 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