Answer in brief
CVE-2026-63975 records a Unknown severity vulnerability in Bluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-63975 records a Unknown severity vulnerability in Bluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=15f02b91056253e8cdc592888f431da0731337b8 <3c8eaa91eb433c450426539290be4ffe282e9f00 || >=15f02b91056253e8cdc592888f431da0731337b8 <ecfed1e0d8efecad6737a0d83e21d2fd021d8c48 || >=15f02b91056253e8cdc592888f431da0731337b8 <e6833e737a51db1e5ea0401322acf5e22abd8be6 || >=15f02b91056253e8cdc592888f431da0731337b8 <6319b38fe69f56ed95680ade485b957a53fff642 || >=15f02b91056253e8cdc592888f431da0731337b8 <291eec1041c918c460dc9702e44edd17794b4a4b || >=15f02b91056253e8cdc592888f431da0731337b8 <41e29548b5e8b5e5fcf708786b3bea67cab107fa || >=15f02b91056253e8cdc592888f431da0731337b8 <d153b8898c0051eb8b6a083b35cbe304a5886bd5 || >=15f02b91056253e8cdc592888f431da0731337b8 <41c2713b204e6cb6a94587bc6bf6935107df5479 | 3c8eaa91eb433c450426539290be4ffe282e9f00, ecfed1e0d8efecad6737a0d83e21d2fd021d8c48, e6833e737a51db1e5ea0401322acf5e22abd8be6, 6319b38fe69f56ed95680ade485b957a53fff642, 291eec1041c918c460dc9702e44edd17794b4a4b, 41e29548b5e8b5e5fcf708786b3bea67cab107fa, d153b8898c0051eb8b6a083b35cbe304a5886bd5, 41c2713b204e6cb6a94587bc6bf6935107df5479 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=15f02b91056253e8cdc592888f431da0731337b8 <3c8eaa91eb433c450426539290be4ffe282e9f00 || >=15f02b91056253e8cdc592888f431da0731337b8 <ecfed1e0d8efecad6737a0d83e21d2fd021d8c48 || >=15f02b91056253e8cdc592888f431da0731337b8 <e6833e737a51db1e5ea0401322acf5e22abd8be6 || >=15f02b91056253e8cdc592888f431da0731337b8 <6319b38fe69f56ed95680ade485b957a53fff642 || >=15f02b91056253e8cdc592888f431da0731337b8 <291eec1041c918c460dc9702e44edd17794b4a4b || >=15f02b91056253e8cdc592888f431da0731337b8 <41e29548b5e8b5e5fcf708786b3bea67cab107fa || >=15f02b91056253e8cdc592888f431da0731337b8 <d153b8898c0051eb8b6a083b35cbe304a5886bd5 || >=15f02b91056253e8cdc592888f431da0731337b8 <41c2713b204e6cb6a94587bc6bf6935107df5479 | 3c8eaa91eb433c450426539290be4ffe282e9f00, ecfed1e0d8efecad6737a0d83e21d2fd021d8c48, e6833e737a51db1e5ea0401322acf5e22abd8be6, 6319b38fe69f56ed95680ade485b957a53fff642, 291eec1041c918c460dc9702e44edd17794b4a4b, 41e29548b5e8b5e5fcf708786b3bea67cab107fa, d153b8898c0051eb8b6a083b35cbe304a5886bd5, 41c2713b204e6cb6a94587bc6bf6935107df5479 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.