{"id":"CVE-2026-11368","published":"2026-08-04T15:16:24.843","lastModified":"2026-08-09T14:26:15.890","description":"The Bluetooth host ATT layer (subsys/bluetooth/host/att.c) associates each in-flight ATT TX buffer with its owning channel via the static tx_meta_data_storage[] array (data->att_chan = chan). When a buffer's last reference is dropped, its net-buf destroy callback defers the completion handling to the system workqueue (att_tx_destroy -> att_tx_destroy_work_handler -> att_on_sent_cb -> bt_att_sent), where bt_att_sent dereferences the channel and its ATT context (sys_slist_get(&att->reqs)).\n\nWhen a peer disconnects while an ATT PDU (a server notification/indication or any response) is still in flight in the controller TX path, L2CAP tears the channel down in l2cap_chan_del(): it runs the disconnected callback and then the released callback (bt_att_released), which frees the channel slab slot. Because the in-flight buffer is held by the connection TX path rather than the channel's own queue, its deferred destroy work can run after the channel has been freed. The att_on_sent_cb guard intended to drop the stale callback itself dereferences meta->att_chan, which is now a dangling pointer into a freed (and possibly reused) slab slot.\n\nA remote peer with an ATT connection can drive this by disconnecting during routine ATT traffic; no pairing or user interaction is required to reach the ATT bearer. The result is a use-after-free read/write of freed channel memory, reliably crashing the Bluetooth host (denial of service) and, because the channel slab slot may be reused, potentially corrupting live memory.\n\nThe fix makes bt_att_released() NULL the att_chan field of every tx_meta_data_storage[] entry still referencing the channel before freeing it, so the deferred guard observes a NULL pointer and drops the callback. Teardown and the destroy work both run on the cooperative system workqueue, so the array update is serialized and needs no lock.","cvssScore":7.1,"cvssSeverity":"HIGH","cvssVector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","cwes":["CWE-416"],"vendors":["zephyrproject"],"products":["zephyr"],"references":[{"url":"https://github.com/zephyrproject-rtos/zephyr/commit/dfdea9bad8d9b5b31c125e97fcffb549f2217caa","tags":["Patch"]},{"url":"https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-85vg-gwc4-77g7","tags":["Exploit","Patch","Vendor Advisory"]}],"exploitRefs":[{"url":"https://github.com/zephyrproject-rtos/zephyr/commit/dfdea9bad8d9b5b31c125e97fcffb549f2217caa","tags":["Patch"]},{"url":"https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-85vg-gwc4-77g7","tags":["Exploit","Patch","Vendor Advisory"]}],"hasPoc":true,"ai":{"summary":"The flaw allows a remote peer to cause a use-after-free condition by disconnecting during an in-flight ATT PDU, leading to potential crashes.","exploitability":"Exploitation is relatively straightforward as it requires only routine disconnection of an active ATT connection; no advanced permissions or user interaction are needed.","blast_radius":"If exploited, the vulnerability could lead to system instability and crashes, impacting devices using Bluetooth communication.","remediation":"Update to the latest version of zephyrproject that includes a fix for this issue.","tags":["remote-exploit","blue-tooth","memory-issues","crash"],"model":"qwen2.5:7b-instruct","analyzedAt":"2026-08-11T07:03:34.723Z"}}