| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2023-53018: Bluetooth: hci_conn: Fix memory leaks |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| Bluetooth: hci_conn: Fix memory leaks |
| |
| When hci_cmd_sync_queue() failed in hci_le_terminate_big() or |
| hci_le_big_terminate(), the memory pointed by variable d is not freed, |
| which will cause memory leak. Add release process to error path. |
| |
| The Linux kernel CVE team has assigned CVE-2023-53018 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.0 with commit eca0ae4aea66914515e5e3098ea051b518ee5316 and fixed in 6.1.9 with commit f51a825b9f730a782aa768454906b4468e67b667 |
| Issue introduced in 6.0 with commit eca0ae4aea66914515e5e3098ea051b518ee5316 and fixed in 6.2 with commit 3aa21311f36d8a2730c7ccef37235e951f23927b |
| |
| 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-53018 |
| 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_conn.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/f51a825b9f730a782aa768454906b4468e67b667 |
| https://git.kernel.org/stable/c/3aa21311f36d8a2730c7ccef37235e951f23927b |
