CVE-2026-53252

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 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 memory leak in error path of hci_alloc_dev()

Early failures in Bluetooth HCI UART configuration leak SRCU percpu memory.

When device initialization fails before hci_register_dev() completes, the HCI_UNREGISTER flag is never set. As a result, when the device reference count reaches zero, bt_host_release() evaluates this flag as false and falls back to a direct kfree(hdev).

Because hci_release_dev() is bypassed, the SRCU struct initialized early in hci_alloc_dev() is never cleaned up, resulting in a leak of percpu memory.

Fix the leak by explicitly calling cleanup_srcu_struct() in the fallback (unregistered) branch of bt_host_release() before freeing the device.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 8, 2026

Advisory Details (7)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

Bluetooth: fix memory leak in error path of hci_alloc_dev() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: fix memory leak in error path of hci_alloc_dev() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: fix memory leak in error path of hci_alloc_dev() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: fix memory leak in error path of hci_alloc_dev() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: fix memory leak in error path of hci_alloc_dev() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: fix memory leak in error path of hci_alloc_dev() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37b3009bf5976e8ab77c8b9a9bc3bbd7ff49e37f
generic

Bluetooth: fix memory leak in error path of hci_alloc_dev() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0622e527a31d4b44737fed5c1a2ac1fc2cfb5184

Vendor Advisories for CVE-2026-53252(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 70× 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-26 15:11 UTCEG score recompute
  2. 2026-07-26 15:11 UTCVendor advisory
  3. 2026-07-26 15:11 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-24 14:18 UTCEPSS rescore
  6. 2026-07-23 14:18 UTCEPSS rescore
  7. 2026-07-23 03:19 UTCEG score recompute
  8. 2026-07-22 14:08 UTCEPSS rescore
  9. 2026-07-21 15:25 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 02:29 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-16 11:35 UTCVendor advisory
  17. 2026-07-16 11:35 UTCGHSA enrichment
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 11:57 UTCVendor advisory
  21. 2026-07-15 11:57 UTCGHSA enrichment
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-14 12:15 UTCVendor advisory
  25. 2026-07-14 12:15 UTCGHSA enrichment
Show 49 more
  1. 2026-07-13 22:31 UTCEPSS rescore
  2. 2026-07-13 12:42 UTCGHSA enrichment
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 13:09 UTCVendor advisory
  6. 2026-07-12 13:09 UTCGHSA enrichment
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 13:35 UTCVendor advisory
  9. 2026-07-11 13:35 UTCGHSA enrichment
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-10 14:02 UTCVendor advisory
  13. 2026-07-10 14:01 UTCGHSA enrichment
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 14:27 UTCEG score recompute▲ 5.50
  17. 2026-07-09 14:27 UTCVendor advisory
  18. 2026-07-09 14:27 UTCGHSA enrichment
  19. 2026-07-08 16:51 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  20. 2026-07-08 15:16 UTCEPSS rescore
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-07 13:46 UTCEPSS rescore
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-06 18:17 UTCVendor advisory
  25. 2026-07-06 18:16 UTCGHSA enrichment
  26. 2026-07-06 16:27 UTCEPSS rescore
  27. 2026-07-06 16:27 UTCEPSS rescore
  28. 2026-07-06 02:23 UTCEPSS rescore
  29. 2026-07-06 02:23 UTCEPSS rescore
  30. 2026-07-05 02:31 UTCEPSS rescore
  31. 2026-07-05 02:30 UTCEPSS rescore
  32. 2026-07-04 06:31 UTCEPSS rescore
  33. 2026-07-04 06:31 UTCEPSS rescore
  34. 2026-07-03 22:14 UTCVendor advisory
  35. 2026-07-03 22:14 UTCGHSA enrichment
  36. 2026-07-01 15:07 UTCEPSS rescore
  37. 2026-07-01 02:12 UTCVendor advisory
  38. 2026-07-01 02:12 UTCGHSA enrichment
  39. 2026-06-30 23:22 UTCEPSS rescore
  40. 2026-06-29 14:06 UTCEPSS rescore
  41. 2026-06-29 14:06 UTCEPSS rescore
  42. 2026-06-28 14:07 UTCEPSS rescore
  43. 2026-06-28 06:09 UTCGHSA enrichment
  44. 2026-06-28 04:56 UTCEPSS rescore
  45. 2026-06-28 04:56 UTCEPSS rescore
  46. 2026-06-27 03:08 UTCEPSS rescore
  47. 2026-06-25 13:49 UTCEPSS rescore
  48. 2026-06-25 10:05 UTCEG score recompute
  49. 2026-06-25 10:04 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53252?
CVE-2026-53252 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix memory leak in error path of hciallocdev() Early failures in Bluetooth HCI UART configuration leak SRCU percpu memory. When device initialization fails before hciregisterdev() completes, the HCI_UNREGISTER flag is…
When was CVE-2026-53252 disclosed?
CVE-2026-53252 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53252 actively exploited?
CVE-2026-53252 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53252?
CVE-2026-53252 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53252?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53252, 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-53252

Explore →

Is Your Infrastructure Affected by CVE-2026-53252?

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

Start Free Scan →Browse All CVEs