Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.8epss 0.2%
exploitation probability
0.2%top 89% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/116b9c002c894097adc2b8684db2d1da4229ed46https://git.kernel.org/stable/c/2112c4c47d36bc5aba3ddeb9afedce6ae6a67e7dhttps://git.kernel.org/stable/c/25e97f7b1866e6b8503be349eeea44bb52d661cehttps://git.kernel.org/stable/c/5134556c9be582793f30695c09d18a26fe1ff2d7https://git.kernel.org/stable/c/55410a9144c76ecda126e6cdec556dfcd8f343b2https://git.kernel.org/stable/c/5f352a56f0e607e6ff539cbf12156bfd8af232behttps://git.kernel.org/stable/c/6a27762340ad08643de3bc17fe1646ea489ca2e2https://git.kernel.org/stable/c/fd269a0435f8e9943b7a57c5a59688848d42d449