Linux vulnerability

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.

Published 19 Jul 2026Updated 2 Oct 20268 sources
CVSS 8.8

What happened

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.

Affected versions

Linux: 15f02b91056253e8cdc592888f431da0731337b8 through before 3c8eaa91eb433c450426539290be4ffe282e9f00 (git); 15f02b91056253e8cdc592888f431da0731337b8 through before ecfed1e0d8efecad6737a0d83e21d2fd021d8c48 (git); 15f02b91056253e8cdc592888f431da0731337b8 through before e6833e737a51db1e5ea0401322acf5e22abd8be6 (git); 15f02b91056253e8cdc592888f431da0731337b8 through before 6319b38fe69f56ed95680ade485b957a53fff642 (git); 15f02b91056253e8cdc592888f431da0731337b8 through before 291eec1041c918c460dc9702e44edd17794b4a4b (git); 15f02b91056253e8cdc592888f431da0731337b8 through before 41e29548b5e8b5e5fcf708786b3bea67cab107fa (git); 15f02b91056253e8cdc592888f431da0731337b8 through before d153b8898c0051eb8b6a083b35cbe304a5886bd5 (git); 15f02b91056253e8cdc592888f431da0731337b8 through before 41c2713b204e6cb6a94587bc6bf6935107df5479 (git); 5.7 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.