Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-90093

Bluetooth: L2CAP: access chan->conn safely in get/setsockopt

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.273, 5.15.224, 6.1.191, 6.6.160, 6.12.114, and 3 more
None on Exploit-DB, Metasploit or GitHub

Summary

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.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 5.10.265 · fixed in 5.10.273; From 5.15.216 · fixed in 5.15.224; From 6.1.183 · fixed in 6.1.191; From 6.6.145 · fixed in 6.6.160; From 6.12.97 · fixed in 6.12.114; From 6.18.39 · fixed in 6.18.57; From 7.1.4 · fixed in 7.2

  • Linux Linux

    7.2

  • KernelLinux

    fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.6

References 8

git.kernel.org