CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's Bluetooth L2CAP implementation, specifically in the handling of connection references during socket option operations. Improper access to potentially invalid connection fields can lead to kernel crashes, posing a risk of denial-of-service attacks. Organizations using Linux systems with Bluetooth capabilities should prioritize patching this issue to maintain system stability and security.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: access chan->conn safely in get/setsockopt Since commit b66774b48dd9 ("Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref") l2cap_chan::conn has held reference and remains non-NULL also after the corresponding hci_conn is deleted. In this state accessing various fields eg. hci_conn::hdev is invalid, which leads to KASAN crash in l2cap_sock_setsockopt() access of conn->hcon->hdev. Check l2cap_chan::conn.hcon corresponds to an alive hci_conn before trying to use it in l2cap_sock.c. Hold l2cap_chan_lock() in getsockopt/setsockopt to ensure it stays alive, and to avoid data races in l2cap_chan fields.