PT-2026-148495
CVE-2026-93672
·
Publicado
2026-11-16
·
Atualizado
2026-11-16
Descrição por
CVSS 3.1
5.3
MédiaMétricasAV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
Explorabilidade
Correção
Impactos
Fornecedores
Produtos afetados
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾