PoC Monitor
← All CVEs
CVE-2026-90092published 17 Sep 2026 16:06 UTCData: JSON · API

Linux

Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.0high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

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

Fixed in bf61a65c6093970e3b50031c4b79ebf3bd411eba, 491e4c60017969b053888029998d2a61f298986a, 2a3a27aaf19bf069720e024ce6fde54e6bf80df9, 87276dc15b559d32757a43b4415c8445fbae06c4, c47339e169bf4a0a4cfabb91351471f67744c2bc, d4bfa78fd67929b62b02013c107973e0c5b7aa9a, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 5.11, 5.16, 7.1

Linux Linux
  • 7.1

Fixed in 0, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3

Mitigation

Upgrade Linux to bf61a65c6093970e3b50031c4b79ebf3bd411eba or 491e4c60017969b053888029998d2a61f298986a or 2a3a27aaf19bf069720e024ce6fde54e6bf80df9 or 87276dc15b559d32757a43b4415c8445fbae06c4 or c47339e169bf4a0a4cfabb91351471f67744c2bc or d4bfa78fd67929b62b02013c107973e0c5b7aa9a or 6.1.188 or 6.6.157 or 6.12.110 or 6.18.52 or 5.11 or 5.16 or 7.1 or later.

Upgrade Linux to 0 or 6.1.188 or 6.6.157 or 6.12.110 or 6.18.52 or 7.2.6 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published17 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.