linux-cve-announce - CVE-2023-54210: Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025123024-CVE-2023-54210-7a73@gregkh>
Date: Tue, 30 Dec 2025 13:13:40 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54210: Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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

Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()

KASAN reports that there's a use-after-free in
hci_remove_adv_monitor(). Trawling through the disassembly, you can
see that the complaint is from the access in bt_dev_dbg() under the
HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because
msft_remove_monitor() can end up freeing the monitor
structure. Specifically:
  hci_remove_adv_monitor() ->
  msft_remove_monitor() ->
  msft_remove_monitor_sync() ->
  msft_le_cancel_monitor_advertisement_cb() ->
  hci_free_adv_monitor()

Let's fix the problem by just stashing the relevant data when it's
still valid.

The Linux kernel CVE team has assigned CVE-2023-54210 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.0 with commit 7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c and fixed in 6.1.42 with commit 0d4d6b083da9b033ddccef72d77f373c819ae3ea
	Issue introduced in 6.0 with commit 7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c and fixed in 6.4.7 with commit bf00c2c8f6254f44ac041aa9a311ae9e0caf692b
	Issue introduced in 6.0 with commit 7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c and fixed in 6.5 with commit de6dfcefd107667ce2dbedf4d9337f5ed557a4a1

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-2023-54210
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_core.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/0d4d6b083da9b033ddccef72d77f373c819ae3ea
	https://git.kernel.org/stable/c/bf00c2c8f6254f44ac041aa9a311ae9e0caf692b
	https://git.kernel.org/stable/c/de6dfcefd107667ce2dbedf4d9337f5ed557a4a1