CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's Bluetooth implementation, specifically in the handling of L2CAP data during disconnection indications. It allows for a use-after-free condition if the L2CAP connection is deleted concurrently, potentially leading to memory corruption or arbitrary code execution. Organizations utilizing Linux systems with Bluetooth capabilities should prioritize this issue to mitigate potential exploitation risks.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via hci_conn_timeout (disc_work) -> hci_proto_disconn_ind -> l2cap_disconn_ind. This is UAF if the l2cap_conn is deleted concurrently. disc_work is disabled sync in hci_conn_del(), so we cannot take hci_dev_lock in disc_work. Fix by using proto_lock to guard l2cap_data, in addition to hdev->lock which is held in other access paths.