CVE-2023-53297Published Sep 16, 2025 · Sep 16Updated 3d ago
Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
Linux
High8.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 348d446762e7c70778df8bafbdf3fa0df2123f58 · < fd269a0435f8e9943b7a57c5a59688848d42d449| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s Bluetooth L2CAP disconnect response handler can trigger a bad unlock balance when a channel lookup returns NULL without the channel lock being acquired. The input does not specify how an attacker could trigger this condition or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with Bluetooth L2CAP should check their versions; affected versions are not specified.