CVE Hunter
›
CVE-2026-93672

CWE-476

MEDIUM CVSS 5.3 NVD

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.

Yayınlanma 16.11.2026
ISO Tarih 2026-11-16
CVSS Sürüm v3.1
Kaynak NVD
CVSS v3.1 Metrikleri
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack Vector Adjacent AV:A
Attack Complexity High AC:H
Privileges Req. None PR:N
User Interaction None UI:N
Scope Unchanged S:U
Confidentiality None C:N
Integrity None I:N
Availability High A:H
AI Güvenlik Analizi
🤖 Yapay Zeka Güvenlik Analizi Hazırlanıyor…
CVSS vektörü ve CWE zayıflık yapısı inceleniyor…
Hedef Keşif Sorguları
CVSS Skoru
5.3 / 10 · CVSS MEDIUM
Zayıflık Türleri (CWE)
CWE-476
Referanslar (2)
İlgili CVE'ler
5.3
CVE-2026-132138
A flaw was found in cyrus-sasl. When processing authentication requests using the Salted Challenge Response Au
0.0
CVE-2026-126706
In Eclipse Mosquitto versions 2.1.0 to 2.1.2, the mosquitto_ctrl utility would crash if attempting to interact
0.0
CVE-2026-129149
In Eclipse Mosquitto versions 2.1.0 to 2.1.2, using the mosquitto_ctrl utility in interactive shell mode to in
7.5
CVE-2026-110339
The Libreswan pluto daemon dereferences a NULL pointer when a CERT payload is received with an empty PKCS#7 pa
5.5
CVE-2026-130062
GPAC before 26.07.0 contains a NULL pointer dereference vulnerability in gf_node_get_tag() that allows attacke
4.7
CVE-2026-93669
The ITE IT8xxx2 SHI host-command backend in subsys/mgmt/ec_host_cmd/backends/ec_host_cmd_backend_shi_ite.c arm