CVE-2026-74540
HighCVSS 8.8Exploitation Probability (EPSS)
Low risk16th percentile - higher than 16% of all known CVEs
Summary
In the Linux kernel, Bluetooth L2CAP has a use-after-free vulnerability in l2cap_le_connect_rsp. The channel is obtained without holding a reference, allowing a concurrent disconnect to free it, leading to use-after-free.
Risk Assessment
The vulnerability can cause system crash or potentially remote code execution by an attacker within Bluetooth range.
Recommendation
Apply the patch that adds l2cap_chan_hold_unless_zero() after ident lookup and l2cap_chan_put() on the exit path.
Original NVD description (English source)
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp l2cap_le_connect_rsp() obtains a channel via __l2cap_get_chan_by_ident() but neither holds a reference nor uses l2cap_chan_hold_unless_zero() before locking and operating on it. A concurrent l2cap_chan_del() triggered by a remote disconnect can free the channel between the lookup and l2cap_chan_lock(), causing a use-after-free. The BR/EDR counterpart l2cap_connect_rsp() and the sibling handler l2cap_le_command_rej() already use l2cap_chan_hold_unless_zero() to safely hold a reference, but l2cap_le_connect_rsp() was left unprotected. Fix by adding l2cap_chan_hold_unless_zero() after the ident lookup and l2cap_chan_put() on the exit path, consistent with other L2CAP response handlers.