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

CVE-2026-53072: Linux Kernel: Bluetooth Connection Locking Issue

CVE-2026-53072
Summary

A locking issue in the Linux kernel's Bluetooth connection handling has been fixed. This issue could have led to a memory corruption error when a Bluetooth connection was deleted while another process was trying to confirm it. The fix ensures that the connection is properly locked to prevent this issue.

What to do

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

Affected software
VendorProductAffected versions
linux linux_kernel >= 3.17, < 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
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER When protocol sets HCI_PROTO_DEFER, hci_conn_request_evt(...
Original description
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER

When protocol sets HCI_PROTO_DEFER, hci_conn_request_evt() calls
hci_connect_cfm(conn) without hdev->lock. Generally hci_connect_cfm()
assumes it is held, and if conn is deleted concurrently -> UAF.

Only SCO and ISO set HCI_PROTO_DEFER and only for defer setup listen,
and HCI_EV_CONN_REQUEST is not generated for ISO. In the non-deferred
listening socket code paths, hci_connect_cfm(conn) is called with
hdev->lock held.

Fix by holding the lock.
nvd CVSS3.1 8.8
Vulnerability type
CWE-667 Improper Locking
Published: 24 Jun 2026 · Updated: 21 Jul 2026 · First seen: 28 Jun 2026