Skip to main content
VulnerabilityPublished

CVE-2026-63948: Linux kernel · Bluetooth: L2CAP: fix chan ref leak in l2cap_chan_timeout() on !conn

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 30 Oct 2026, 16:18 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Linux LinuxAffected
  • 4.19.314 – 6.8.10
7 affected builds
Fixed in–

AI-suggested

A fix for this vulnerability is available in the specified Linux kernel versions. Users should update to these fixed versions to remediate the issue. No additional mitigation is required beyond applying the official patch.

Description

A reference leak vulnerability in the Linux kernel's Bluetooth L2CAP implementation was fixed. The flaw involved a missing reference release in the l2cap_chan_timeout() function when the channel's connection pointer was NULL, causing a reference leak. This was addressed by adding the missing l2cap_chan_put() call before the early return in the function.

References

Community reviews

Loading reviews…