CVE-2026-53072

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.8
EG Score
8.8(high)
EPSS
15.9%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c7777f534a8018ae4bb1c80d8925af4df588a314
generic

Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c27224daf0b08efbb2b24ed64b6139b294f5473a
generic

Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d4a6c0f43fc5e4d4f062e8e450e5483eb74176e
generic

Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b4d226d01ab7da0d2027a2a1e3a6079152e5065
generic

Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60e3f4ff02d1f2d55bfbf2ca32a97285a9771ee4
generic

Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c7209a341ff2ac338b2b0375c34a307b37c9ac2
generic

Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/541d5bf9b5afaf41090b2a3aa7b47f2db2ff801f
generic

Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/385b2d0468a0871fc716c549fa3b0c257c7dbcb3

Vendor Advisories for CVE-2026-53072(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 37× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 06:54 UTCEG score recompute
  2. 2026-07-07 06:53 UTCGHSA enrichment
  3. 2026-07-06 18:33 UTCEG score recompute
  4. 2026-07-06 18:33 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 06:16 UTCEG score recompute
  8. 2026-07-06 06:16 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 17:33 UTCEG score recompute
  12. 2026-07-05 17:33 UTCGHSA enrichment
  13. 2026-07-05 05:16 UTCEG score recompute
  14. 2026-07-05 05:16 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 16:51 UTCEG score recompute
  18. 2026-07-04 16:50 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 04:32 UTCEG score recompute
  21. 2026-07-04 04:32 UTCGHSA enrichment
  22. 2026-07-03 16:12 UTCEG score recompute
  23. 2026-07-03 16:12 UTCGHSA enrichment
  24. 2026-07-03 03:57 UTCEG score recompute
  25. 2026-07-03 03:56 UTCGHSA enrichment
Show 24 more
  1. 2026-07-02 15:41 UTCEG score recompute
  2. 2026-07-02 15:41 UTCGHSA enrichment
  3. 2026-07-02 03:25 UTCEG score recompute
  4. 2026-07-02 03:25 UTCGHSA enrichment
  5. 2026-07-01 15:09 UTCEG score recompute
  6. 2026-07-01 15:09 UTCGHSA enrichment
  7. 2026-07-01 15:07 UTCEPSS rescore
  8. 2026-07-01 02:54 UTCEG score recompute
  9. 2026-07-01 02:54 UTCGHSA enrichment
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-30 14:38 UTCEG score recompute▲ 8.80
  12. 2026-06-30 14:37 UTCGHSA enrichment
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 16:23 UTCEG score recompute
  20. 2026-06-27 16:23 UTCGHSA enrichment
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-24 18:14 UTCEG score recompute
  24. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53072?
CVE-2026-53072 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix locking in hciconnrequestevt() with HCIPROTO_DEFER When protocol sets HCIPROTODEFER, hciconnrequest_evt() calls hciconnectcfm(conn) without hdev->lock. Generally hciconnectcfm() assumes it is held, and if conn is…
When was CVE-2026-53072 disclosed?
CVE-2026-53072 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53072 actively exploited?
CVE-2026-53072 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53072?
CVE-2026-53072 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-53072?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53072, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53072

Explore →

Is Your Infrastructure Affected by CVE-2026-53072?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs