In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: fix UAF in l2capleconnect_rsp
l2capleconnect_rsp() obtains a channel via __l2capgetchanbyident() but neither holds a reference nor uses l2capchanholdunlesszero() before locking and operating on it. A concurrent l2capchandel() triggered by a remote disconnect can free the channel between the lookup and l2capchanlock(), causing a use-after-free.
The BR/EDR counterpart l2capconnectrsp() and the sibling handler l2caplecommandrej() already use l2capchanholdunlesszero() to safely hold a reference, but l2capleconnectrsp() was left unprotected.
Fix by adding l2capchanholdunlesszero() after the ident lookup and l2capchanput() on the exit path, consistent with other L2CAP response handlers.
{
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/74xxx/CVE-2026-74540.json"
}