Bluetooth: L2CAP: access chan->conn safely in get/setsockopt
CVE-2026-90093 · published 17 Sept 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-90093?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 91047a4396a8b1857a6f712a90cf33ec0012b189 to < 19e154d794eb4d33d99ca4a087b1cea9d5e65786, 0b0e2bf39cf99e458d991b9df253727e036a7d7d to < 3af72bf8f73c519ee562e6963d5ff8e678924f93, d3b739db5dc6f688a60d56da872fabaf65246032 to < 8460dc49c9756a1e9288218060b4d41e1b704905, b66774b48dd98f07254951f74ea6f513efe7ff8b to < f49321c85785178214fd67f2e9b4b73d6363783b
- Linux Linux: 7.2
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/19e154d794eb4d33d99ca4a087b1cea9d5e65786
- git.kernel.org/stable/c/3af72bf8f73c519ee562e6963d5ff8e678924f93
- git.kernel.org/stable/c/8460dc49c9756a1e9288218060b4d41e1b704905
- git.kernel.org/stable/c/f49321c85785178214fd67f2e9b4b73d6363783b
- git.kernel.org/stable/c/ca2c4c26498643f421d35ffe258fafbd3ed461c3
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON