[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025032716-CVE-2023-53017-8dd9@gregkh>
Date: Thu, 27 Mar 2025 17:44:04 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2023-53017: Bluetooth: hci_sync: fix memory leak in hci_update_adv_data()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_sync: fix memory leak in hci_update_adv_data()
When hci_cmd_sync_queue() failed in hci_update_adv_data(), inst_ptr is
not freed, which will cause memory leak, convert to use ERR_PTR/PTR_ERR
to pass the instance to callback so no memory needs to be allocated.
The Linux kernel CVE team has assigned CVE-2023-53017 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1 with commit 651cd3d65b0f76a2198fcf3a80ce5d53dd267717 and fixed in 6.1.9 with commit 8ac6043bd3e5b58d30f50737aedc2e58e8087ad5
Issue introduced in 6.1 with commit 651cd3d65b0f76a2198fcf3a80ce5d53dd267717 and fixed in 6.2 with commit 1ed8b37cbaf14574c779064ef1372af62e8ba6aa
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-53017
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_sync.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/8ac6043bd3e5b58d30f50737aedc2e58e8087ad5
https://git.kernel.org/stable/c/1ed8b37cbaf14574c779064ef1372af62e8ba6aa
Powered by blists - more mailing lists