CVE-2023-53762

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-08. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync

Use-after-free can occur in hci_disconnect_all_sync if a connection is deleted by concurrent processing of a controller event.

To prevent this the code now tries to iterate over the list backwards to ensure the links are cleanup before its parents, also it no longer relies on a cursor, instead it always uses the last element since hci_abort_conn_sync is guaranteed to call hci_conn_del.

UAF crash log: ================================================================== BUG: KASAN: slab-use-after-free in hci_set_powered_sync (net/bluetooth/hci_sync.c:5424) [bluetooth] Read of size 8 at addr ffff888009d9c000 by task kworker/u9:0/124

CPU: 0 PID: 124 Comm: kworker/u9:0 Tainted: G W 6.5.0-rc1+ #10 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-1.fc38 04/01/2014 Workqueue: hci0 hci_cmd_sync_work [bluetooth] Call Trace: dump_stack_lvl+0x5b/0x90 print_report+0xcf/0x670 ? __virt_addr_valid+0xdd/0x160 ? hci_set_powered_sync+0x2c9/0x4a0 [bluetooth] kasan_report+0xa6/0xe0 ? hci_set_powered_sync+0x2c9/0x4a0 [bluetooth] ? __pfx_set_powered_sync+0x10/0x10 [bluetooth] hci_set_powered_sync+0x2c9/0x4a0 [bluetooth] ? __pfx_hci_set_powered_sync+0x10/0x10 [bluetooth] ? __pfx_lock_release+0x10/0x10 ? __pfx_set_powered_sync+0x10/0x10 [bluetooth] hci_cmd_sync_work+0x137/0x220 [bluetooth] process_one_work+0x526/0x9d0 ? __pfx_process_one_work+0x10/0x10 ? __pfx_do_raw_spin_lock+0x10/0x10 ? mark_held_locks+0x1a/0x90 worker_thread+0x92/0x630 ? __pfx_worker_thread+0x10/0x10 kthread+0x196/0x1e0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50

Allocated by task 1782: kasan_save_stack+0x33/0x60 kasan_set_track+0x25/0x30 __kasan_kmalloc+0x8f/0xa0 hci_conn_add+0xa5/0xa80 [bluetooth] hci_bind_cis+0x881/0x9b0 [bluetooth] iso_connect_cis+0x121/0x520 [bluetooth] iso_sock_connect+0x3f6/0x790 [bluetooth] __sys_connect+0x109/0x130 __x64_sys_connect+0x40/0x50 do_syscall_64+0x60/0x90 entry_SYSCALL_64_after_hwframe+0x6e/0xd8

Freed by task 695: kasan_save_stack+0x33/0x60 kasan_set_track+0x25/0x30 kasan_save_free_info+0x2b/0x50 __kasan_slab_free+0x10a/0x180 __kmem_cache_free+0x14d/0x2e0 device_release+0x5d/0xf0 kobject_put+0xdf/0x270 hci_disconn_complete_evt+0x274/0x3a0 [bluetooth] hci_event_packet+0x579/0x7e0 [bluetooth] hci_rx_work+0x287/0xaa0 [bluetooth] process_one_work+0x526/0x9d0 worker_thread+0x92/0x630 kthread+0x196/0x1e0 ret_from_fork+0x2c/0x50 ==================================================================

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

December 8, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94d9ba9f9888b748d4abd2aa1547af56ae85f772
generic

Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a30c074f0b5b7f909a15c978fbc96a29e2f94e42

Vendor Advisories for CVE-2023-53762(6)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-284.158.1.el9_22026-02-25redhat
redhatkernel-rt-0:5.14.0-284.158.1.rt14.443.el9_22026-02-25redhat
redhatkernel-rt-0:4.18.0-553.105.1.rt7.446.el8_102026-02-17redhat
redhatkernel-0:4.18.0-553.105.1.el8_102026-02-16redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 6.4.16—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.5.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.5.3-1—

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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.

Showing the most recent 100 of 188 total refreshes for this CVE.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-16 05:11 UTCEPSS rescore
  4. 2026-09-16 05:11 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-13 16:45 UTCEPSS rescore
  7. 2026-09-12 14:58 UTCEPSS rescore
  8. 2026-09-12 07:10 UTCOSV refresh
  9. 2026-09-11 14:51 UTCEPSS rescore
  10. 2026-09-11 09:34 UTCEPSS rescore
  11. 2026-09-08 21:58 UTCEPSS rescore
  12. 2026-09-07 15:59 UTCEPSS rescore
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-05 15:26 UTCEPSS rescore
  15. 2026-09-04 13:58 UTCEPSS rescore
  16. 2026-09-04 05:04 UTCEPSS rescore
  17. 2026-09-02 14:10 UTCEPSS rescore
  18. 2026-09-01 13:52 UTCEPSS rescore
  19. 2026-09-01 04:36 UTCEPSS rescore
  20. 2026-08-30 19:15 UTCEPSS rescore
  21. 2026-08-30 01:20 UTCEPSS rescore
  22. 2026-08-28 21:39 UTCEPSS rescore
  23. 2026-08-27 14:23 UTCEPSS rescore
  24. 2026-08-26 14:44 UTCEPSS rescore
  25. 2026-08-25 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-24 12:22 UTCOSV refresh
  2. 2026-08-23 00:17 UTCEPSS rescore
  3. 2026-08-23 00:17 UTCEPSS rescore
  4. 2026-08-21 23:47 UTCEPSS rescore
  5. 2026-08-20 22:53 UTCEPSS rescore
  6. 2026-08-19 17:02 UTCEPSS rescore
  7. 2026-08-18 13:46 UTCEPSS rescore
  8. 2026-08-16 14:54 UTCEPSS rescore
  9. 2026-08-16 02:12 UTCEPSS rescore
  10. 2026-08-15 01:28 UTCEPSS rescore
  11. 2026-08-13 21:58 UTCEPSS rescore
  12. 2026-08-12 13:49 UTCEPSS rescore
  13. 2026-08-11 13:40 UTCEPSS rescore
  14. 2026-08-10 23:58 UTCEPSS rescore
  15. 2026-08-09 13:44 UTCEPSS rescore
  16. 2026-08-08 16:35 UTCEPSS rescore
  17. 2026-08-08 08:16 UTCEG score recompute
  18. 2026-08-08 08:16 UTCVendor advisory
  19. 2026-08-08 08:16 UTCGHSA enrichment
  20. 2026-08-07 16:25 UTCEPSS rescore
  21. 2026-08-06 13:45 UTCEPSS rescore
  22. 2026-08-05 19:15 UTCEPSS rescore
  23. 2026-08-05 19:15 UTCEPSS rescore
  24. 2026-08-05 10:15 UTCEG score recompute
  25. 2026-08-05 10:15 UTCVendor advisory
  26. 2026-08-05 10:15 UTCGHSA enrichment
  27. 2026-08-04 10:54 UTCEG score recompute
  28. 2026-08-04 10:54 UTCVendor advisory
  29. 2026-08-04 10:53 UTCGHSA enrichment
  30. 2026-08-04 10:36 UTCEPSS rescore
  31. 2026-08-04 09:27 UTCEG score recompute▲ 8.80
  32. 2026-08-04 09:27 UTCVendor advisory
  33. 2026-08-04 09:27 UTCGHSA enrichment
  34. 2026-08-04 09:20 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  35. 2026-08-03 10:34 UTCEPSS rescore
  36. 2026-08-02 02:25 UTCEPSS rescore
  37. 2026-08-02 02:25 UTCEPSS rescore
  38. 2026-08-01 04:14 UTCEPSS rescore
  39. 2026-07-30 16:26 UTCEPSS rescore
  40. 2026-07-30 01:29 UTCEPSS rescore
  41. 2026-07-28 15:34 UTCEPSS rescore
  42. 2026-07-28 15:34 UTCEPSS rescore
  43. 2026-07-27 05:39 UTCOSV refresh
  44. 2026-07-26 14:53 UTCEPSS rescore
  45. 2026-07-25 14:16 UTCEPSS rescore
  46. 2026-07-24 14:16 UTCEPSS rescore
  47. 2026-07-23 14:16 UTCEPSS rescore
  48. 2026-07-23 02:29 UTCEG score recompute
  49. 2026-07-22 23:16 UTCEG score recompute
  50. 2026-07-22 14:07 UTCEPSS rescore
  51. 2026-07-22 14:07 UTCEPSS rescore
  52. 2026-07-21 15:23 UTCEPSS rescore
  53. 2026-07-20 17:06 UTCEPSS rescore
  54. 2026-07-19 02:27 UTCEPSS rescore
  55. 2026-07-19 02:27 UTCEPSS rescore
  56. 2026-07-18 10:03 UTCEPSS rescore
  57. 2026-07-18 10:03 UTCEPSS rescore
  58. 2026-07-16 17:01 UTCEPSS rescore
  59. 2026-07-15 16:56 UTCEPSS rescore
  60. 2026-07-15 01:59 UTCEPSS rescore
  61. 2026-07-15 01:59 UTCEPSS rescore
  62. 2026-07-13 22:28 UTCEPSS rescore
  63. 2026-07-13 22:28 UTCEPSS rescore
  64. 2026-07-13 06:11 UTCEPSS rescore
  65. 2026-07-12 05:45 UTCEPSS rescore
  66. 2026-07-12 05:45 UTCEPSS rescore
  67. 2026-07-11 08:26 UTCEPSS rescore
  68. 2026-07-10 00:17 UTCOSV refresh
  69. 2026-07-09 19:08 UTCEPSS rescore
  70. 2026-07-08 15:13 UTCEPSS rescore
  71. 2026-07-07 13:45 UTCEPSS rescore
  72. 2026-07-07 13:44 UTCEPSS rescore
  73. 2026-07-06 16:26 UTCEPSS rescore
  74. 2026-07-06 16:26 UTCEPSS rescore
  75. 2026-07-06 02:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-53762?
CVE-2023-53762 is a high vulnerability published on December 8, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcisync: Fix UAF in hcidisconnectallsync Use-after-free can occur in hcidisconnectall_sync if a connection is deleted by concurrent processing of a controller event. To prevent this the code now tries to iterate over the…
When was CVE-2023-53762 disclosed?
CVE-2023-53762 was first published in the National Vulnerability Database on December 8, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53762 actively exploited?
CVE-2023-53762 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.9% of all scored CVEs.
What is the CVSS score of CVE-2023-53762?
CVE-2023-53762 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-53762?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53762, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53762

Explore →

Is Your Infrastructure Affected by CVE-2023-53762?

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

Start Free Scan →Browse All CVEs