CVE-2026-63948Published Jul 19, 2026 · Jul 19Updated 3d ago
Bluetooth: L2CAP: fix chan ref leak in l2cap_chan_timeout() on !conn
Linux
Medium5.5Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ adf0398cee86643b8eacde95f17d073d022f782c · < e8a5baff5be273ca07771fd2b9bb1f2a4152917b| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux