[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091626-CVE-2023-53293-73cb@gregkh>
Date: Tue, 16 Sep 2025 10:11:43 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53293: Bluetooth: btrtl: check for NULL in btrtl_set_quirks()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btrtl: check for NULL in btrtl_set_quirks()
The btrtl_set_quirks() has accessed btrtl_dev->ic_info->lmp_subver since
b8e482d02513. However, if installing a Realtek Bluetooth controller
without the driver supported, it will hit the NULL point accessed.
Add a check for NULL to avoid the Kernel Oops.
The Linux kernel CVE team has assigned CVE-2023-53293 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.30 with commit ea160ece08668a30ce69f92cc08e87da54a64a9c
Fixed in 6.3.4 with commit c34722f0bb9f7efb0e7e7a75a9cb57601132b51f
Fixed in 6.4 with commit 253cf30e8d3d001850a95c4729d668f916b037ab
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-53293
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:
drivers/bluetooth/btrtl.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/ea160ece08668a30ce69f92cc08e87da54a64a9c
https://git.kernel.org/stable/c/c34722f0bb9f7efb0e7e7a75a9cb57601132b51f
https://git.kernel.org/stable/c/253cf30e8d3d001850a95c4729d668f916b037ab
Powered by blists - more mailing lists