Bluetooth: L2CAP: fix chan ref leak in l2cap_chan_timeout() on !conn
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 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 chan ref leak in l2cap_chan_timeout() on !conn
__set_chan_timer() takes a l2cap_chan reference via l2cap_chan_hold()
before scheduling the delayed work. The normal path in
l2cap_chan_timeout() drops this reference with l2cap_chan_put() at the
end, but the early return when chan->conn is NULL skips the put,
leaking the reference.
Add the missing l2cap_chan_put() before the early return.
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/08d81fe96f80a8e20c7acb573b6a45d901fcf2cdhttps://git.kernel.org/stable/c/107c826e4ef9ec5ad8f60e6fe64d8d5325ba508fhttps://git.kernel.org/stable/c/50f1bcaaaa3a80bb1c3472044bc146e8d49d51eehttps://git.kernel.org/stable/c/63cd225cc13d782a85e2a73c04d0d350153eada1https://git.kernel.org/stable/c/8894c2010435a56ce7c6c2a8785860c13554df2fhttps://git.kernel.org/stable/c/9dbd84990394c51f5cee1e8871bb5ff8af5ed939https://git.kernel.org/stable/c/b5c59a5b469e2a809a2d57eda4ded94235971060https://git.kernel.org/stable/c/e8a5baff5be273ca07771fd2b9bb1f2a4152917b