All vulnerabilities

Servers and applications

CVE-2026-53252

Bluetooth: fix memory leak in error path of hci_alloc_dev()

Severity
Unrated
Published
25 Jun 2026
Last changed
6 Nov 2026
Added to UpHeron
6 Nov 2026
Fixed in
6.1.176, 6.6.143, 6.12.94, 6.16, 6.18.36, 7.0.13
Exploit chance
0.1% in the next 30 daysHigher than 2% of CVEs. EPSS by FIRST, 19 Nov 2026
Sources
CVE Program

Description

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

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.

From the CVE Program.

Affected software

SoftwareAffected versions
Linux kernelServers and applications · cna:linux|linux
  • From 6.19 before 7.0.13
  • From 6.16 before 5.15.210
  • From 6.15.5 before 6.16
  • From 6.13 before 6.18.36
All 12 release lines
  • From 5.10.259 before 5.11
  • From 5.15.209 before 5.15.210
  • From 5.16 before 6.1.176
  • From 6.1.167 before 6.1.176
  • From 6.2 before 6.6.143
  • From 6.6.97 before 6.6.143
  • From 6.7 before 6.12.94
  • From 6.12.36 before 6.12.94
  • From 6.13 before 6.18.36
  • From 6.15.5 before 6.16
  • From 6.16 before 5.15.210
  • From 6.19 before 7.0.13

About Linux kernel

Unix-like operating system kernel, basis for all Linux operating systems

From Wikidata, CC0 1.0.
GitHub stars
255,726GitHub, 15 Nov 2026
Forks
67,394GitHub, 15 Nov 2026
Developer
Linus TorvaldsWikidata
License
GNU General Public License, version 2.0Wikidata
Written in
CWikidata
First released
25 Aug 1991Wikidata
First published on GitHub
4 Sept 2011GitHub

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-53252