CVE-2026-63948: Bluetooth: L2CAP: fix chan ref leak in l2cap_chan_timeout() on !conn
Published Jul 19, 2026
·
Updated
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: fix chan ref leak in l2capchantimeout() on !conn
setchantimer() takes a l2capchan reference via l2capchanhold()
before scheduling the delayed work. The normal path in
l2capchantimeout() drops this reference with l2capchanput() at the
end, but the early return when chan->conn is NULL skips the put,
leaking the reference.
Add the missing l2capchanput() before the early return.
The leak occurs when l2cap_chan_timeout() runs while chan->conn is NULL. In that early-return path, the reference acquired by __set_chan_timer() is not released.
2
What is the impact described by the fix?
The described impact is a leaked L2CAP channel reference. The provided data does not specify a remote attack vector, privilege requirement, or a concrete consequence such as denial of service.
3
How can I determine whether the issue is fixed in my kernel source?
Inspect l2cap_chan_timeout() for the early-return path handling a NULL chan->conn value. The fixed code calls l2cap_chan_put() before returning from that path.
SecAlerts Pty Ltd. 132 Wickham Terrace Fortitude Valley, QLD 4006, Australia info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.