CVE-2026-63948

Bluetooth: L2CAP: fix chan ref leak in l2cap_chan_timeout() on !conn

MEDIUM
5.5
CVSS Score
Published: July 19, 2026 at 02:55 PM UTC
Updated: October 30, 2026 at 02:27 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19.314 ≤ v < 4.205.10.217 ≤ v < 5.10.2595.15.159 ≤ v < 5.15.2105.4.276 ≤ v < 5.56.1.91 ≤ v < 6.1.1766.13 ≤ v < 6.18.356.19 ≤ v < 7.0.126.6.31 ≤ v < 6.6.1436.8.10 ≤ v < 6.96.9.1 ≤ v < 6.12.934.19.3145.10.2175.15.1595.4.2766.1.916.6.316.8.106.96466ee65e5b27161c846c73ef407f49dfa1bd1d96acb75e7ed600d0bbf7bff5628aa8f24a97978c7.18960ff650aec70485b40771cd8e6e8c4cb467d33955b5b6c54d95b5e7444dfc81c95c8e013f27ac0adf0398cee86643b8eacde95f17d073d022f782ce137e2ba96e51902dc2878131823a96bf8e638aee97e16433eb4533083b096a3824b93a5ca3aee79eb86f955488c39526534211f2610e48a5cf8ead4
Vendor states this is fixed in 08d81fe96f80a8e20c7acb573b6a45d901fcf2cd (fixed)
Vendor states this is fixed in 107c826e4ef9ec5ad8f60e6fe64d8d5325ba508f (fixed)
Vendor states this is fixed in 50f1bcaaaa3a80bb1c3472044bc146e8d49d51ee (fixed)
Vendor states this is fixed in 63cd225cc13d782a85e2a73c04d0d350153eada1 (fixed)
Vendor states this is fixed in 8894c2010435a56ce7c6c2a8785860c13554df2f (fixed)
Vendor states this is fixed in 9dbd84990394c51f5cee1e8871bb5ff8af5ed939 (fixed)
Vendor states this is fixed in b5c59a5b469e2a809a2d57eda4ded94235971060 (fixed)
Vendor states this is fixed in e8a5baff5be273ca07771fd2b9bb1f2a4152917b (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.93 (unaffected)
Vendor states this is fixed in 6.18.35 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)
Vendor states this is fixed in 7.0.12 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card