CVE-2026-53252Bluetooth: fix memory leak in error path of hci_alloc_dev()
- 5.5MediumCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 16 days later
· 16 days later
Published
- 4 months later
· 4 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 90dee0a0ff84fac8accd5be98412b3819f667149 – < 5b7dfca6f852e6b9d809fd0263b5427cc9fb33fd
- affected c56b177efce8b62798e4d96bdb9867106cb7c4a0 – < c016118b9e51eeaf5bc93850d4c455a3b583c0aa
- affected bc0819a25e04cd68ef3568cfa51b63118fea39a7 – < 0622e527a31d4b44737fed5c1a2ac1fc2cfb5184
- affected ce23b73f0f27e2dbeb81734a79db710f05aa33c6 – < bc2efe73c194a74839d7cf57b63880d97e21d309
- affected 1d6123102e9fbedc8d25bf4731da6d513173e49e – < ce4b4cac3c5749b6aa75e62e2991ae2263f2f889
- affected 1d6123102e9fbedc8d25bf4731da6d513173e49e – < f82799407a50af7bcacacf09cc9b279af8fe9b81
- affected 1d6123102e9fbedc8d25bf4731da6d513173e49e – < 37b3009bf5976e8ab77c8b9a9bc3bbd7ff49e37f
- affected dd4becd3fd4102696e1c15e6d260a1712a2d8685
- affected 0e5c144c557df910ab64d9c25d06399a9a735e65
- affected 5.15.209 – < 5.15.210
- affected 6.1.167 – < 6.1.176
- affected 6.6.97 – < 6.6.143
- affected 6.12.36 – < 6.12.94
- affected 5.10.259 – < 5.11
- affected 6.15.5 – < 6.16
- affected 6.16
- unaffected < 6.16
- unaffected 5.15.210 – ≤ 5.15.*
- unaffected 6.1.176 – ≤ 6.1.*
- unaffected 6.6.143 – ≤ 6.6.*
- unaffected 6.12.94 – ≤ 6.12.*
- unaffected 6.18.36 – ≤ 6.18.*
- unaffected 7.0.13 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References7
- https://git.kernel.org/stable/c/5b7dfca6f852e6b9d809fd0263b5427cc9fb33fd (opens in a new tab)
- https://git.kernel.org/stable/c/c016118b9e51eeaf5bc93850d4c455a3b583c0aa (opens in a new tab)
- https://git.kernel.org/stable/c/0622e527a31d4b44737fed5c1a2ac1fc2cfb5184 (opens in a new tab)
- https://git.kernel.org/stable/c/bc2efe73c194a74839d7cf57b63880d97e21d309 (opens in a new tab)
- https://git.kernel.org/stable/c/ce4b4cac3c5749b6aa75e62e2991ae2263f2f889 (opens in a new tab)
- https://git.kernel.org/stable/c/f82799407a50af7bcacacf09cc9b279af8fe9b81 (opens in a new tab)
- https://git.kernel.org/stable/c/37b3009bf5976e8ab77c8b9a9bc3bbd7ff49e37f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-39203 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-53252)Record last updated .