CVE-2023-53297
Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.14.316, 4.19.284, 5.4.244, 5.10.181, 5.15.113, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 4.14.313 · fixed in 4.14.316; From 4.19.281 · fixed in 4.19.284; From 5.4.241 · fixed in 5.4.244; From 5.10.178 · fixed in 5.10.181; From 5.15.108 · fixed in 5.15.113; From 6.1.25 · fixed in 6.1.30; From 6.2.12 · fixed in 6.3
- Linux Linux
6.3
References 8
git.kernel.org
- stable/c/5f352a56f0e607e6ff539cbf12156bfd8af232be
- stable/c/6a27762340ad08643de3bc17fe1646ea489ca2e2
- stable/c/2112c4c47d36bc5aba3ddeb9afedce6ae6a67e7d
- stable/c/55410a9144c76ecda126e6cdec556dfcd8f343b2
- stable/c/116b9c002c894097adc2b8684db2d1da4229ed46
- stable/c/fd269a0435f8e9943b7a57c5a59688848d42d449
- stable/c/5134556c9be582793f30695c09d18a26fe1ff2d7
- stable/c/25e97f7b1866e6b8503be349eeea44bb52d661ce