Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
8.8

CVE-2026-53071: Linux Bluetooth: Missing Lock Causes Channel Corruption

CVE-2026-53071 CVE-2026-53071
Summary

A security issue in the Linux Bluetooth system can allow a remote device to corrupt the channel list, potentially causing system instability or crashes. This issue has been fixed in the latest Linux kernel updates. If you use Linux with Bluetooth, it's recommended to update your system to the latest version to ensure you have this fix.

What to do

No fix is available yet. Check with your software vendor for updates.

Affected software
VendorProductAffected versions
linux linux < 96dca51715d86559ed6ed8028e5445cecb80f3ae
5.7
linux linux_kernel >= 5.7, < 5.10.258
>= 5.11, < 5.15.209
>= 5.16, < 6.1.175
>= 6.2, < 6.6.141
>= 6.7, < 6.12.91
>= 6.13, < 6.18.33
>= 6.19, < 7.0.10
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Original title
Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp
Original description
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp

l2cap_ecred_reconf_rsp() calls l2cap_chan_del() without holding
l2cap_chan_lock(). Every other l2cap_chan_del() caller in the file
acquires the lock first. A remote BLE device can send a crafted
L2CAP ECRED reconfiguration response to corrupt the channel list
while another thread is iterating it.

Add l2cap_chan_hold() and l2cap_chan_lock() before l2cap_chan_del(),
and l2cap_chan_unlock() and l2cap_chan_put() after, matching the
pattern used in l2cap_ecred_conn_rsp() and l2cap_conn_del().
nvd CVSS3.1 8.8
Vulnerability type
CWE-416 Use After Free
CWE-667 Improper Locking
Published: 24 Jun 2026 · Updated: 22 Jul 2026 · First seen: 28 Jun 2026