Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 43 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-90093, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 8f90405a4a6f1f1880dc07996b47bf57c712bd8a – < c66cd500ba1a58b3798c468fcc774ed2c8c2ec7d
    • affected 32d783cafb46ff3ca58e6f9fd62c9c5f35eaf26b – < 737b80c97aef10404a9beed7c0ed45fcd5fc5931
    • affected 8922c7940bae9ce4b1736dddb6362370793835c2 – < 0d7b7b31ea092e17d757bd24e2e9028ba5e3a4ca
    • affected 91047a4396a8b1857a6f712a90cf33ec0012b189 – < 19e154d794eb4d33d99ca4a087b1cea9d5e65786
    • affected 0b0e2bf39cf99e458d991b9df253727e036a7d7d – < 3af72bf8f73c519ee562e6963d5ff8e678924f93
    • affected d3b739db5dc6f688a60d56da872fabaf65246032 – < 8460dc49c9756a1e9288218060b4d41e1b704905
    • affected b66774b48dd98f07254951f74ea6f513efe7ff8b – < f49321c85785178214fd67f2e9b4b73d6363783b
    • affected b66774b48dd98f07254951f74ea6f513efe7ff8b – < ca2c4c26498643f421d35ffe258fafbd3ed461c3
    • affected 50c38d9f42a529691e4e67ea9cedf4f0bfc8d277
    • affected 5.10.265 – < 5.10.273
    • affected 5.15.216 – < 5.15.224
    • affected 6.1.183 – < 6.1.191
    • affected 6.6.145 – < 6.6.160
    • affected 6.12.97 – < 6.12.114
    • affected 6.18.39 – < 6.18.57
    • affected 7.1.4 – < 7.2
  • Linux · Linux

    • affected 7.2
    • unaffected < 7.2
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90093 badge
[![CVE-2026-90093](https://cveledger.app/badge/CVE-2026-90093.svg)](https://cveledger.app/cve/CVE-2026-90093)

Record last updated .