Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63948, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (22 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 06acb75e7ed600d0bbf7bff5628aa8f24a97978c – < 50f1bcaaaa3a80bb1c3472044bc146e8d49d51ee
    • affected e97e16433eb4533083b096a3824b93a5ca3aee79 – < b5c59a5b469e2a809a2d57eda4ded94235971060
    • affected 8960ff650aec70485b40771cd8e6e8c4cb467d33 – < 8894c2010435a56ce7c6c2a8785860c13554df2f
    • affected 955b5b6c54d95b5e7444dfc81c95c8e013f27ac0 – < 63cd225cc13d782a85e2a73c04d0d350153eada1
    • affected adf0398cee86643b8eacde95f17d073d022f782c – < 107c826e4ef9ec5ad8f60e6fe64d8d5325ba508f
    • affected adf0398cee86643b8eacde95f17d073d022f782c – < e8a5baff5be273ca07771fd2b9bb1f2a4152917b
    • affected adf0398cee86643b8eacde95f17d073d022f782c – < 08d81fe96f80a8e20c7acb573b6a45d901fcf2cd
    • affected adf0398cee86643b8eacde95f17d073d022f782c – < 9dbd84990394c51f5cee1e8871bb5ff8af5ed939
    • affected e137e2ba96e51902dc2878131823a96bf8e638ae
    • affected 6466ee65e5b27161c846c73ef407f49dfa1bd1d9
    • affected eb86f955488c39526534211f2610e48a5cf8ead4
    • affected 5.10.217 – < 5.10.259
    • affected 5.15.159 – < 5.15.210
    • affected 6.1.91 – < 6.1.176
    • affected 6.6.31 – < 6.6.143
    • affected 4.19.314 – < 4.20
    • affected 5.4.276 – < 5.5
    • affected 6.8.10 – < 6.9
  • Linux · Linux

    • affected 6.9
    • unaffected < 6.9
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63948 badge
[![CVE-2026-63948](https://cveledger.app/badge/CVE-2026-63948.svg)](https://cveledger.app/cve/CVE-2026-63948)

Record last updated .