[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091641-CVE-2023-53305-b8fe@gregkh>
Date: Tue, 16 Sep 2025 18:11:50 +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-53305: Bluetooth: L2CAP: Fix use-after-free
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: Fix use-after-free
Fix potential use-after-free in l2cap_le_command_rej.
The Linux kernel CVE team has assigned CVE-2023-53305 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.324 with commit e76bab1b7afa580cd76362540fc37551ada4359b
Fixed in 4.19.293 with commit 1a40c56e8bff3e424724d78a9a6b3272dd8a371d
Fixed in 5.4.255 with commit fe49aa73cca6608714477b74bfc6874b9db979df
Fixed in 5.10.192 with commit 2958cf9f805b9f0bdc4a761bf6ea281eb8d44f8e
Fixed in 5.15.128 with commit 548a6b64b3c0688f01119a6fcccceb41f8c984e4
Fixed in 6.1.47 with commit 149daab45922ab1ac7f0cbeacab7251a46bf5e63
Fixed in 6.4.12 with commit 255be68150291440657b2cdb09420b69441af3d8
Fixed in 6.5 with commit f752a0b334bb95fe9b42ecb511e0864e2768046f
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-53305
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/l2cap_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/e76bab1b7afa580cd76362540fc37551ada4359b
https://git.kernel.org/stable/c/1a40c56e8bff3e424724d78a9a6b3272dd8a371d
https://git.kernel.org/stable/c/fe49aa73cca6608714477b74bfc6874b9db979df
https://git.kernel.org/stable/c/2958cf9f805b9f0bdc4a761bf6ea281eb8d44f8e
https://git.kernel.org/stable/c/548a6b64b3c0688f01119a6fcccceb41f8c984e4
https://git.kernel.org/stable/c/149daab45922ab1ac7f0cbeacab7251a46bf5e63
https://git.kernel.org/stable/c/255be68150291440657b2cdb09420b69441af3d8
https://git.kernel.org/stable/c/f752a0b334bb95fe9b42ecb511e0864e2768046f
Powered by blists - more mailing lists