CVE-2026-63948
Bluetooth: L2CAP: fix chan ref leak in l2cap_chan_timeout() on !conn
- 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 5.10.259, 5.15.210, 6.1.176, 6.6.143, 4.20, 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
Summary
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.
Timeline
- CVE published
Affected versions
- Linux Linux
From 5.10.217 · fixed in 5.10.259; From 5.15.159 · fixed in 5.15.210; From 6.1.91 · fixed in 6.1.176; From 6.6.31 · fixed in 6.6.143; From 4.19.314 · fixed in 4.20; From 5.4.276 · fixed in 5.5; From 6.8.10 · fixed in 6.9
- Linux Linux
6.9
References 8
git.kernel.org
- stable/c/50f1bcaaaa3a80bb1c3472044bc146e8d49d51ee
- stable/c/b5c59a5b469e2a809a2d57eda4ded94235971060
- stable/c/8894c2010435a56ce7c6c2a8785860c13554df2f
- stable/c/63cd225cc13d782a85e2a73c04d0d350153eada1
- stable/c/107c826e4ef9ec5ad8f60e6fe64d8d5325ba508f
- stable/c/e8a5baff5be273ca07771fd2b9bb1f2a4152917b
- stable/c/08d81fe96f80a8e20c7acb573b6a45d901fcf2cd
- stable/c/9dbd84990394c51f5cee1e8871bb5ff8af5ed939