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

CVE record · `CVE-2026-90093`

- **Identifiers:** `CVE-2026-90093`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 17 Sept 2026
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 17 Sept 2026, 16:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `8f90405a4a6f1f1880dc07996b47bf57c712bd8a to before c66cd500ba1a58b3798c468fcc774ed2c8c2ec7d` (git)
  - affected: `32d783cafb46ff3ca58e6f9fd62c9c5f35eaf26b to before 737b80c97aef10404a9beed7c0ed45fcd5fc5931` (git)
  - affected: `8922c7940bae9ce4b1736dddb6362370793835c2 to before 0d7b7b31ea092e17d757bd24e2e9028ba5e3a4ca` (git)
  - affected: `91047a4396a8b1857a6f712a90cf33ec0012b189 to before 19e154d794eb4d33d99ca4a087b1cea9d5e65786` (git)
  - affected: `0b0e2bf39cf99e458d991b9df253727e036a7d7d to before 3af72bf8f73c519ee562e6963d5ff8e678924f93` (git)
  - affected: `d3b739db5dc6f688a60d56da872fabaf65246032 to before 8460dc49c9756a1e9288218060b4d41e1b704905` (git)
  - affected: `b66774b48dd98f07254951f74ea6f513efe7ff8b to before f49321c85785178214fd67f2e9b4b73d6363783b` (git)
  - affected: `b66774b48dd98f07254951f74ea6f513efe7ff8b to before ca2c4c26498643f421d35ffe258fafbd3ed461c3` (git)
  - affected: `50c38d9f42a529691e4e67ea9cedf4f0bfc8d277` (git)
  - affected: `5.10.265 to before 5.10.273` (semver)
  - affected: `5.15.216 to before 5.15.224` (semver)
  - affected: `6.1.183 to before 6.1.191` (semver)
  - and 4 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `7.2`
  - unaffected: `before 7.2` (semver)
  - unaffected: `5.10.273 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.224 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.160 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.114 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.57 to 6.18.*, inclusive` (semver)
  - unaffected: `7.2.6 to 7.2.*, inclusive` (semver)
  - unaffected: `7.3 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's Bluetooth L2CAP socket option handling can access a connection object after it has been deleted, which the description says can cause a KASAN crash. The source gives few details on what an attacker needs to trigger this. Upgrade to the fixed stable releases for your branch: 5.10.273, 5.15.224, 6.1.191, or 6.6.160 or later. The source lists no fixed release for 7.2.

Written 12 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0018, the 7th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 17 Sept 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-90093](https://www.cve.org/CVERecord?id=CVE-2026-90093)
- [NVD: CVE-2026-90093](https://nvd.nist.gov/vuln/detail/CVE-2026-90093)

### References from the CNA

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

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-90093>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-90093/>. Everything for agents: <https://agentprime.io/llms.txt>.