CVE-2023-53297: Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
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.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53297 is a Linux kernel Bluetooth L2CAP bug that can trigger a bad lock/unlock state and affect system availability. The published CVSS score is 5.5, with local access and low privileges required. Treat it as operationally important on Linux systems where Bluetooth is enabled or kernel exposure is difficult to rule out.
Executive priority
Handle in the normal kernel patch cycle, with higher priority for shared workstations, multi-user systems, and endpoints where Bluetooth is enabled. There is no cited active exploitation, but the availability impact makes delayed patching a reliability and operations risk.
Technical view
The issue is in l2cap_disconnect_rsp. The CVE states conn->chan_lock is not acquired before l2cap_get_chan_by_scid; if that lookup returns NULL, a bad unlock balance is triggered. The impact is availability only under the provided CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Likely exposure
Exposure is most likely on Linux systems running affected kernel builds with Bluetooth/L2CAP support present. The source bundle lists multiple Linux stable branches and fix commits, but affected version encoding is not fully clear. Confirm against the exact vendor kernel package, not only upstream version strings.
Exploitation context
No active exploitation is stated in the bundle, and KEV is false. The CVSS vector indicates a local, low-privilege attacker could trigger high availability impact without user interaction. The sources do not provide evidence of remote exploitation or public weaponization.
Researcher notes
The core defect is lock-state handling in the Bluetooth L2CAP disconnect response path. The source bundle provides upstream stable commit references but no CWE, proof-of-concept, or detailed exploit conditions. Avoid over-claiming affected products beyond Linux kernel builds and downstream packages that include the vulnerable code.
Mitigation direction
Update to a vendor kernel build containing the referenced Linux stable fixes.
Prioritize systems where Bluetooth is enabled or local user access is broad.
Check Linux distribution advisories for backported fixes before relying on version numbers.
Disable or restrict Bluetooth where it is unnecessary and operationally safe.
Track kernel package rollout through standard patch management controls.
Validation and detection
Inventory Linux kernel versions and distribution package revisions across managed assets.
Confirm whether deployed kernels include the referenced stable commit fixes.
Check whether Bluetooth support is enabled or loaded on affected systems.
Review vendor advisories for backport status and reboot requirements.
Validate patched systems are running the updated kernel after reboot.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-53297 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.