CVE-2026-90256
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/2b66c83ff1751d6bd3201b3017206262ab46dc05
- git.kernel.org/stable/c/b495a3a9b33bc4e4613e685bf5c96c136caa22d8
- git.kernel.org/stable/c/0fa448369c87e20b2aeaeaca0187d698dd61f791
- git.kernel.org/stable/c/7c032b6d48a46634cbd58aaebad2638c00ad3b51
- nvd.nist.gov/vuln/detail/CVE-2026-90256
- cve.org/CVERecord?id=CVE-2026-90256
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.