CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's Bluetooth L2CAP implementation, where improper handling of connection responses can lead to a potential crash. This issue arises when a destination channel ID (dcid) is received for an already-assigned channel, risking system stability. Organizations using Linux systems with Bluetooth capabilities should prioritize this fix to mitigate the risk of crashes and ensure reliable operation.
Original NVD 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.