Review reviewHigh

CVE-2026-53072

Linux Linux, linux kernel

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.

CVSS
8.8
EPSS
0.19%
9.52% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.19%
Technical severityCVSS 8.8

Vulnerability overview

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.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 70c464256310e1c3716099b9d02ece4169272f73 < 60e3f4ff02d1f2d55bfbf2ca32a97285a9771ee4, >= 70c464256310e1c3716099b9d02ece4169272f73 < 9d4a6c0f43fc5e4d4f062e8e450e5483eb74176e, >= 70c464256310e1c3716099b9d02ece4169272f73 < c7777f534a8018ae4bb1c80d8925af4df588a314, >= 70c464256310e1c3716099b9d02ece4169272f73 < 6b4d226d01ab7da0d2027a2a1e3a6079152e5065, >= 70c464256310e1c3716099b9d02ece4169272f73 < 541d5bf9b5afaf41090b2a3aa7b47f2db2ff801f, >= 70c464256310e1c3716099b9d02ece4169272f73 < 385b2d0468a0871fc716c549fa3b0c257c7dbcb3, >= 70c464256310e1c3716099b9d02ece4169272f73 < c27224daf0b08efbb2b24ed64b6139b294f5473a, >= 70c464256310e1c3716099b9d02ece4169272f73 < 5c7209a341ff2ac338b2b0375c34a307b37c9ac2, >= 3.17, >= 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
Fixed versions
5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

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