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-63975Bluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp If dcid is received for an already-assigned destination CID the spec requires that both channels to be discarded, but calling l2cap_chan_del may invalidate the tmp cursor created by list_for_each_entry_safe and in fact it is the wrong procedure as the chan->dcid may be assigned previously it really needs to be disconnected. Calling l2cap_chan_clone directly may still lead to l2cap_chan_del so instead schedule l2cap_chan_timeout with delay 0 to close the channel asynchronously.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

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-63975, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.27% · top 80% of all CVEs (22 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 15f02b91056253e8cdc592888f431da0731337b8 – < 3c8eaa91eb433c450426539290be4ffe282e9f00
    • affected 15f02b91056253e8cdc592888f431da0731337b8 – < ecfed1e0d8efecad6737a0d83e21d2fd021d8c48
    • affected 15f02b91056253e8cdc592888f431da0731337b8 – < e6833e737a51db1e5ea0401322acf5e22abd8be6
    • affected 15f02b91056253e8cdc592888f431da0731337b8 – < 6319b38fe69f56ed95680ade485b957a53fff642
    • affected 15f02b91056253e8cdc592888f431da0731337b8 – < 291eec1041c918c460dc9702e44edd17794b4a4b
    • affected 15f02b91056253e8cdc592888f431da0731337b8 – < 41e29548b5e8b5e5fcf708786b3bea67cab107fa
    • affected 15f02b91056253e8cdc592888f431da0731337b8 – < d153b8898c0051eb8b6a083b35cbe304a5886bd5
    • affected 15f02b91056253e8cdc592888f431da0731337b8 – < 41c2713b204e6cb6a94587bc6bf6935107df5479
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • 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-63975 badge
[![CVE-2026-63975](https://cveledger.app/badge/CVE-2026-63975.svg)](https://cveledger.app/cve/CVE-2026-63975)

Record last updated .