CVE-2023-53252

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-15. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

Bluetooth: use RCU for hci_conn_params and iterate safely in hci_sync

hci_update_accept_list_sync iterates over hdev->pend_le_conns and hdev->pend_le_reports, and waits for controller events in the loop body, without holding hdev lock.

Meanwhile, these lists and the items may be modified e.g. by le_scan_cleanup. This can invalidate the list cursor or any other item in the list, resulting to invalid behavior (eg use-after-free).

Use RCU for the hci_conn_params action lists. Since the loop bodies in hci_sync block and we cannot use RCU or hdev->lock for the whole loop, copy list items first and then iterate on the copy. Only the flags field is written from elsewhere, so READ_ONCE/WRITE_ONCE should guarantee we read valid values.

Free params everywhere with hci_conn_params_free so the cleanup is guaranteed to be done properly.

This fixes the following, which can be triggered e.g. by BlueZ new mgmt-tester case "Add + Remove Device Nowait - Success", or by changing hci_le_set_cig_params to always return false, and running iso-tester:

================================================================== BUG: KASAN: slab-use-after-free in hci_update_passive_scan_sync (net/bluetooth/hci_sync.c:2536 net/bluetooth/hci_sync.c:2723 net/bluetooth/hci_sync.c:2841) Read of size 8 at addr ffff888001265018 by task kworker/u3:0/32

Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-1.fc38 04/01/2014 Workqueue: hci0 hci_cmd_sync_work Call Trace:

dump_stack_lvl (./arch/x86/include/asm/irqflags.h:134 lib/dump_stack.c:107) print_report (mm/kasan/report.c:320 mm/kasan/report.c:430) ? __virt_addr_valid (./include/linux/mmzone.h:1915 ./include/linux/mmzone.h:2011 arch/x86/mm/physaddr.c:65) ? hci_update_passive_scan_sync (net/bluetooth/hci_sync.c:2536 net/bluetooth/hci_sync.c:2723 net/bluetooth/hci_sync.c:2841) kasan_report (mm/kasan/report.c:538) ? hci_update_passive_scan_sync (net/bluetooth/hci_sync.c:2536 net/bluetooth/hci_sync.c:2723 net/bluetooth/hci_sync.c:2841) hci_update_passive_scan_sync (net/bluetooth/hci_sync.c:2536 net/bluetooth/hci_sync.c:2723 net/bluetooth/hci_sync.c:2841) ? __pfx_hci_update_passive_scan_sync (net/bluetooth/hci_sync.c:2780) ? mutex_lock (kernel/locking/mutex.c:282) ? __pfx_mutex_lock (kernel/locking/mutex.c:282) ? __pfx_mutex_unlock (kernel/locking/mutex.c:538) ? __pfx_update_passive_scan_sync (net/bluetooth/hci_sync.c:2861) hci_cmd_sync_work (net/bluetooth/hci_sync.c:306) process_one_work (./arch/x86/include/asm/preempt.h:27 kernel/workqueue.c:2399) worker_thread (./include/linux/list.h:292 kernel/workqueue.c:2538) ? __pfx_worker_thread (kernel/workqueue.c:2480) kthread (kernel/kthread.c:376) ? __pfx_kthread (kernel/kthread.c:331) ret_from_fork (arch/x86/entry/entry_64.S:314)

Allocated by task 31: kasan_save_stack (mm/kasan/common.c:46) kasan_set_track (mm/kasan/common.c:52) __kasan_kmalloc (mm/kasan/common.c:374 mm/kasan/common.c:383) hci_conn_params_add (./include/linux/slab.h:580 ./include/linux/slab.h:720 net/bluetooth/hci_core.c:2277) hci_connect_le_scan (net/bluetooth/hci_conn.c:1419 net/bluetooth/hci_conn.c:1589) hci_connect_cis (net/bluetooth/hci_conn.c:2266) iso_connect_cis (net/bluetooth/iso.c:390) iso_sock_connect (net/bluetooth/iso.c:899) __sys_connect (net/socket.c:2003 net/socket.c:2020) __x64_sys_connect (net/socket.c:2027) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)

Freed by task 15: kasan_save_stack (mm/kasan/common.c:46) kasan_set_track (mm/kasan/common.c:52) kasan_save_free_info (mm/kasan/generic.c:523) __kasan_slab_free (mm/kasan/common.c:238 mm/kasan/common.c:200 mm/kasan/common.c:244) __kmem_cache_free (mm/slub.c:1807 mm/slub.c:3787 mm/slub.c:3800) hci_conn_params_del (net/bluetooth/hci_core.c:2323) le_scan_cleanup (net/bluetooth/hci_conn.c:202) process_one_work (./arch/x86/include/asm/preempt. ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 15, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
Patch available.
Web page

Bluetooth: use RCU for hci_conn_params and iterate safely in hci_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/195ef75e19287b4bc413da3e3e3722b030ac881e
Web page

Bluetooth: use RCU for hci_conn_params and iterate safely in hci_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cef88a0fd8e9c2e838162fbb742b3e713b811a7e
Web page

Bluetooth: use RCU for hci_conn_params and iterate safely in hci_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13ad45ad14df992a6754a130a19abc8c142d54e2

Vendor Advisories for CVE-2023-53252(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 6.1.42 (fixes >=5.17.0)—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 rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.11-1: fixed in 6.4.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.11-1: fixed in 6.4.11-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 92 of 189 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-20 21:16 UTCEG score recompute
  5. 2026-10-20 21:16 UTCVendor advisory
  6. 2026-10-20 21:16 UTCGHSA enrichmentGHSA-r8x4-762h-wj65 · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-19 14:55 UTCOSV refresh
  10. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-18 07:41 UTCEG score recompute
  12. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-12 18:12 UTCEG score recompute
  18. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-11 21:38 UTCEG score recompute
  20. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 67 more
  1. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-09-30 16:37 UTCEG score recompute
  6. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-09-26 21:11 UTCOSV refresh
  10. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  13. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  14. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  15. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  16. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  17. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  18. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  19. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  20. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  21. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  22. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  23. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  24. 2026-09-07 06:48 UTCOSV refresh
  25. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  26. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  27. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  28. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  29. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  30. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  31. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  32. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  33. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  34. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  35. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  36. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  37. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  38. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  39. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  40. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  41. 2026-08-20 16:31 UTCOSV refresh
  42. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  43. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  44. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  45. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  46. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  48. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  50. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  51. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  52. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  54. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  55. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  56. 2026-08-05 10:20 UTCEG score recompute
  57. 2026-08-05 10:20 UTCVendor advisory
  58. 2026-08-05 10:20 UTCGHSA enrichmentGHSA-r8x4-762h-wj65 · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  60. 2026-08-04 09:33 UTCEG score recompute
  61. 2026-08-04 09:33 UTCVendor advisory
  62. 2026-08-04 09:32 UTCGHSA enrichmentGHSA-r8x4-762h-wj65 · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  65. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  66. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-53252?
CVE-2023-53252 is a high-severity vulnerability; its CVE record was published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: use RCU for hciconnparams and iterate safely in hci_sync hciupdateacceptlistsync iterates over hdev->pendleconns and hdev->pendlereports, and waits for controller events in the loop body, without holding hdev lock.…
When was the CVE record for CVE-2023-53252 published?
The CVE record for CVE-2023-53252 was published on September 15, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53252 actively exploited?
CVE-2023-53252 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53252?
CVE-2023-53252 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53252?
A fix for CVE-2023-53252 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53252 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2023-53252?

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

Book a Demo →Browse All CVEs