From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-53252: Bluetooth: fix memory leak in error path of hci_alloc_dev()
Date: Thu, 25 Jun 2026 09:41:40 +0100 [thread overview]
Message-ID: <2026062514-CVE-2026-53252-4306@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-53252 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15.209 with commit 90dee0a0ff84fac8accd5be98412b3819f667149 and fixed in 5.15.210 with commit 5b7dfca6f852e6b9d809fd0263b5427cc9fb33fd
Issue introduced in 6.1.167 with commit c56b177efce8b62798e4d96bdb9867106cb7c4a0 and fixed in 6.1.176 with commit c016118b9e51eeaf5bc93850d4c455a3b583c0aa
Issue introduced in 6.6.97 with commit bc0819a25e04cd68ef3568cfa51b63118fea39a7 and fixed in 6.6.143 with commit 0622e527a31d4b44737fed5c1a2ac1fc2cfb5184
Issue introduced in 6.12.36 with commit ce23b73f0f27e2dbeb81734a79db710f05aa33c6 and fixed in 6.12.94 with commit bc2efe73c194a74839d7cf57b63880d97e21d309
Issue introduced in 6.16 with commit 1d6123102e9fbedc8d25bf4731da6d513173e49e and fixed in 6.18.36 with commit ce4b4cac3c5749b6aa75e62e2991ae2263f2f889
Issue introduced in 6.16 with commit 1d6123102e9fbedc8d25bf4731da6d513173e49e and fixed in 7.0.13 with commit f82799407a50af7bcacacf09cc9b279af8fe9b81
Issue introduced in 6.16 with commit 1d6123102e9fbedc8d25bf4731da6d513173e49e and fixed in 7.1 with commit 37b3009bf5976e8ab77c8b9a9bc3bbd7ff49e37f
Issue introduced in 5.10.259 with commit dd4becd3fd4102696e1c15e6d260a1712a2d8685
Issue introduced in 6.15.5 with commit 0e5c144c557df910ab64d9c25d06399a9a735e65
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-53252
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
net/bluetooth/hci_sysfs.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/5b7dfca6f852e6b9d809fd0263b5427cc9fb33fd
https://git.kernel.org/stable/c/c016118b9e51eeaf5bc93850d4c455a3b583c0aa
https://git.kernel.org/stable/c/0622e527a31d4b44737fed5c1a2ac1fc2cfb5184
https://git.kernel.org/stable/c/bc2efe73c194a74839d7cf57b63880d97e21d309
https://git.kernel.org/stable/c/ce4b4cac3c5749b6aa75e62e2991ae2263f2f889
https://git.kernel.org/stable/c/f82799407a50af7bcacacf09cc9b279af8fe9b81
https://git.kernel.org/stable/c/37b3009bf5976e8ab77c8b9a9bc3bbd7ff49e37f
reply other threads:[~2026-06-25 9:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026062514-CVE-2026-53252-4306@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox