CVE-2026-63975
Bluetooth: 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.
INFO
Published Date :
July 19, 2026, 4:17 p.m.
Last Modified :
July 30, 2026, 2:51 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Solution
- Apply the Linux kernel patch for the Bluetooth L2CAP vulnerability.
- Ensure L2CAP channel deletion logic correctly handles assigned CIDs.
- Schedule asynchronous channel closure instead of direct deletion.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-63975.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-63975 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-63975
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-63975 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-63975 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 20, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 19, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '15f02b91056253e8cdc592888f431da0731337b8', 'lessThan': '3c8eaa91eb433c450426539290be4ffe282e9f00', 'versionType': 'git'}, {'status': 'affected', 'version': '15f02b91056253e8cdc592888f431da0731337b8', 'lessThan': 'ecfed1e0d8efecad6737a0d83e21d2fd021d8c48', 'versionType': 'git'}, {'status': 'affected', 'version': '15f02b91056253e8cdc592888f431da0731337b8', 'lessThan': 'e6833e737a51db1e5ea0401322acf5e22abd8be6', 'versionType': 'git'}, {'status': 'affected', 'version': '15f02b91056253e8cdc592888f431da0731337b8', 'lessThan': '6319b38fe69f56ed95680ade485b957a53fff642', 'versionType': 'git'}, {'status': 'affected', 'version': '15f02b91056253e8cdc592888f431da0731337b8', 'lessThan': '291eec1041c918c460dc9702e44edd17794b4a4b', 'versionType': 'git'}, {'status': 'affected', 'version': '15f02b91056253e8cdc592888f431da0731337b8', 'lessThan': '41e29548b5e8b5e5fcf708786b3bea67cab107fa', 'versionType': 'git'}, {'status': 'affected', 'version': '15f02b91056253e8cdc592888f431da0731337b8', 'lessThan': 'd153b8898c0051eb8b6a083b35cbe304a5886bd5', 'versionType': 'git'}, {'status': 'affected', 'version': '15f02b91056253e8cdc592888f431da0731337b8', 'lessThan': '41c2713b204e6cb6a94587bc6bf6935107df5479', 'versionType': 'git'}], 'programFiles': ['net/bluetooth/l2cap_core.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.7'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.7', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.259', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.176', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.93', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.35', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.12', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/bluetooth/l2cap_core.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/291eec1041c918c460dc9702e44edd17794b4a4b Added Reference https://git.kernel.org/stable/c/3c8eaa91eb433c450426539290be4ffe282e9f00 Added Reference https://git.kernel.org/stable/c/41c2713b204e6cb6a94587bc6bf6935107df5479 Added Reference https://git.kernel.org/stable/c/41e29548b5e8b5e5fcf708786b3bea67cab107fa Added Reference https://git.kernel.org/stable/c/6319b38fe69f56ed95680ade485b957a53fff642 Added Reference https://git.kernel.org/stable/c/d153b8898c0051eb8b6a083b35cbe304a5886bd5 Added Reference https://git.kernel.org/stable/c/e6833e737a51db1e5ea0401322acf5e22abd8be6 Added Reference https://git.kernel.org/stable/c/ecfed1e0d8efecad6737a0d83e21d2fd021d8c48