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
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 62× 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 192 total refreshes for this CVE.

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

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

See which npm, PyPI, Go, and Maven packages are affected by 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.