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-90092Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN New sk should not be added to parent socket accept queue after last l2cap_sock_cleanup_listen() has run in l2cap_sock_teardown_cb() and state set to BT_CLOSED, as that can result to UAF on dereferencing the dangling parent reference. l2cap_sock_new_connection_cb() may race with parent l2cap_chan teardown, due to chan->state accessed without consistent locking: [Task 1] [Task 2] l2cap_sock_release(parent) l2cap_connect l2cap_sock_shutdown pchan = l2cap_global_chan_by_psm l2cap_chan_lock(pchan) l2cap_chan_close l2cap_sock_teardown_cb pchan->state = BT_CLOSED l2cap_chan_unlock(pchan) ------> l2cap_chan_lock(pchan) l2cap_new_connection l2cap_sock_new_connection_cb l2cap_chan_lock(pchan) <-------- l2cap_chan_unlock(pchan) l2cap_sock_kill(parent) /* bt_sk(sk)->parent dangling */ Fix by adding check for sk_state == BT_LISTEN after acquiring sk lock in l2cap_sock_new_connection_cb(). Add lock_sock() around sk_state writes where missing, to avoid data races. Although the data races on pchan->state should be fixed too, this defensive sk_state check probably makes sense in any case.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 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-90092, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.0CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High8.0CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.36% · top 70% 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 8.0.

Affected products

  • Linux · Linux

    • affected 0c17c8832562b2aac288e89cefd0f46074f54bcb – < bf61a65c6093970e3b50031c4b79ebf3bd411eba
    • affected 5105f3e6b2df619c635b5f6a49fac131a36c7952 – < 491e4c60017969b053888029998d2a61f298986a
    • affected c88c185ae0a1067823661b220aeea613df2c127b – < 2a3a27aaf19bf069720e024ce6fde54e6bf80df9
    • affected 1810e42ff6716f320c7269d5850eca48b07b7427 – < 87276dc15b559d32757a43b4415c8445fbae06c4
    • affected 2ff1a41a912de8517b4482e946dd951b7d80edbf – < c47339e169bf4a0a4cfabb91351471f67744c2bc
    • affected 2ff1a41a912de8517b4482e946dd951b7d80edbf – < d4bfa78fd67929b62b02013c107973e0c5b7aa9a
    • affected 1b1c0da227bf63479bac9982fc8d12df9aaea0fb
    • affected 85426e97dc72f2088ba6d27e74cd58c3fbd43e31
    • affected a2dcf1a61d056aef15b63c6eae9441344d624389
    • affected 6.1.175 – < 6.1.188
    • affected 6.6.140 – < 6.6.157
    • affected 6.12.88 – < 6.12.110
    • affected 6.18.30 – < 6.18.52
    • affected 5.10.258 – < 5.11
    • affected 5.15.209 – < 5.16
    • affected 7.0.7 – < 7.1
  • Linux · Linux

    • affected 7.1
    • unaffected < 7.1
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .