Back to CVE catalog
CVE-2026-11368

Use-After-Free in Bluetooth ATT Stack

zephyrproject zephyr

At a glance

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)). When 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. A 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…

Full source 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)). When 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. A 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. The 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.

Source description · CVE List / CNA

System impact

Attack complexityLow
ConfidentialityNone
IntegrityLow
AvailabilityHigh

CVSS summary v3.1

7.1High
Published:
Updated:
EPSS:
0.301%
Exploited in attacks:
Not confirmed
Ransomware campaigns:
Not confirmed
Attack vector:
Adjacent

Affected software

Vendor, product and affected version ranges.

Vendor, product and affected versions
Vendor:zephyrprojectzephyrAffected versions:
≥ 4.4.0, < 4.4.2

1–1 of 1 · Page 1 of 1

CVSS scores and metrics4
zephyr · CVE List / CNA (cna)Primary7.1 / 10HighCVSS 3.1Details
Attack complexity
Low
Confidentiality
None
Integrity
Low
Availability
High
Attack vector
Adjacent
Privileges required
Not required
User interaction
Not required
Scope
Unchanged

Source vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
[email protected] · NVD (Secondary)7.1 / 10HighCVSS 3.1Details
Attack complexity
Low
Confidentiality
None
Integrity
Low
Availability
High
Attack vector
Adjacent
Privileges required
Not required
User interaction
Not required
Scope
Unchanged

Source vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
[email protected] · NVD (Primary)6.5 / 10MediumCVSS 3.1Details
Attack complexity
Low
Confidentiality
None
Integrity
None
Availability
High
Attack vector
Adjacent
Privileges required
Not required
User interaction
Not required
Scope
Unchanged

Source vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVE-2026-11368 · OSV (source-vector)7.1 / 10HighCVSS 3.1Details
Attack complexity
Low
Confidentiality
None
Integrity
Low
Availability
High
Attack vector
Adjacent
Privileges required
Not required
User interaction
Not required
Scope
Unchanged

Source vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

CVSS measures severity; EPSS estimates exploitation probability. Lack of confirmed attacks does not mean lack of risk.

Sources and advisories8

This product uses the NVD API but is not endorsed or certified by the NVD. CVE® records © The MITRE Corporation, reproduced under the CVE Terms of Use. Data sources and licences