CVE-2026-63975
Last modified
CVE-2026-63975 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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.. EPSS estimates a 0.35% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.7, < 5.10.259 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.93 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.35 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.12 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-63975?
How severe is CVE-2026-63975?
How do I fix CVE-2026-63975?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-6397The Sticky plugin for WordPress is vulnerable to Stored Cros…6.4
- CVE-2026-63970In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63971In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63972In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-63973In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-63974In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63976In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63977In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63978In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-63979In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-6398Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-63980In the Linux kernel, the following vulnerability has been re…7.5
Are you affected by CVE-2026-63975?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST