[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091627-CVE-2023-53297-8746@gregkh>
Date: Tue, 16 Sep 2025 10:11:47 +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-53297: Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
conn->chan_lock isn't acquired before l2cap_get_chan_by_scid,
if l2cap_get_chan_by_scid returns NULL, then 'bad unlock balance'
is triggered.
The Linux kernel CVE team has assigned CVE-2023-53297 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.316 with commit 5f352a56f0e607e6ff539cbf12156bfd8af232be
Fixed in 4.19.284 with commit 6a27762340ad08643de3bc17fe1646ea489ca2e2
Fixed in 5.4.244 with commit 2112c4c47d36bc5aba3ddeb9afedce6ae6a67e7d
Fixed in 5.10.181 with commit 55410a9144c76ecda126e6cdec556dfcd8f343b2
Fixed in 5.15.113 with commit 116b9c002c894097adc2b8684db2d1da4229ed46
Fixed in 6.1.30 with commit fd269a0435f8e9943b7a57c5a59688848d42d449
Fixed in 6.3.4 with commit 5134556c9be582793f30695c09d18a26fe1ff2d7
Fixed in 6.4 with commit 25e97f7b1866e6b8503be349eeea44bb52d661ce
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-53297
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/5f352a56f0e607e6ff539cbf12156bfd8af232be
https://git.kernel.org/stable/c/6a27762340ad08643de3bc17fe1646ea489ca2e2
https://git.kernel.org/stable/c/2112c4c47d36bc5aba3ddeb9afedce6ae6a67e7d
https://git.kernel.org/stable/c/55410a9144c76ecda126e6cdec556dfcd8f343b2
https://git.kernel.org/stable/c/116b9c002c894097adc2b8684db2d1da4229ed46
https://git.kernel.org/stable/c/fd269a0435f8e9943b7a57c5a59688848d42d449
https://git.kernel.org/stable/c/5134556c9be582793f30695c09d18a26fe1ff2d7
https://git.kernel.org/stable/c/25e97f7b1866e6b8503be349eeea44bb52d661ce
Powered by blists - more mailing lists