Read the docs
TI-2026-61135 Aliases CVE-2026-90092GHSA-6f8j-3px9-h4jj

Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN

Priority LOW 35Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
Partial Red Hat: 2 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat.

Summary

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.

Why it matters now

EPSS 0.00362 30th percentileScored 2026-11-07
Fix Partial Linux (Linux): 6.1.188, 6.6.157, 6.12.110 +6Red Hat: 2 without a fix

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
LinuxLinux6.1.175 to before 6.1.188; 6.6.140 to before 6.6.157; 6.12.88 to before 6.12.110; 6.18.30 to before 6.18.52; 5.10.258 to before 5.11; 5.15.209 to before 5.16; 7.0.7 to before 7.16.1.188, 6.6.157, 6.12.110, 6.18.52, 5.11, 5.16, 7.1Patch availableCNA
LinuxLinux7.1 and later6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3Patch availableCNA
  • Linux VendorLinux Affected 6.1.175 to before 6.1.188; 6.6.140 to before 6.6.157; 6.12.88 to before 6.12.110; 6.18.30 to before 6.18.52; 5.10.258 to before 5.11; 5.15.209 to before 5.16; 7.0.7 to before 7.1 Fixed in 6.1.188, 6.6.157, 6.12.110, 6.18.52, 5.11, 5.16, 7.1 Patch available CNA
  • Linux VendorLinux Affected 7.1 and later Fixed in 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*——Linux
  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* Versions — — ·Linux

Remediation

  • Fix · CNA Linux (Linux) Fixed in 6.1.188, 6.6.157, 6.12.110, 6.18.52, 5.11, 5.16, 7.1
  • Fix · CNA Linux (Linux) Fixed in 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Enterprise Linux 10AffectedNo fix yet: Fix deferred
Red Hat Enterprise Linux 9AffectedNo fix yet: Fix deferred
Not affected: 6 products
  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • Red Hat OpenShift Container Platform 4
  • Red Hat OpenShift Container Platform 5

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-90092
  2. 2026-10-03 Alias added: GHSA-6f8j-3px9-h4jj
  3. 2026-10-13 Affected versions changed · Red Hat
  4. 2026-10-13 CVSS score added · Red Hat
  5. 2026-10-19 Fix available: Linux/[email protected] · CNA
  6. 2026-10-24 Affected versions changed · Red Hat
  7. 2026-10-24 CVSS score changed · Red Hat
  8. 2026-10-29 Affected versions changed · Red Hat
  9. 2026-11-06 Affected versions changed · Red Hat

References

  • TI-2025-26358 tls: fix handling of zero-length records on the rx_list KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-38352 netfilter: bridge: make ebt_snat ARP rewrite writable KEVCVSS 3.1HIGH 8.8
  • TI-2021-02452 Incorrect authorization in Ubuntu linux kernel KEVCVSS 3.1HIGH 8.8
  • TI-2013-05264 The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the… KEVCVSS 3.1HIGH 8.8
  • TI-2022-00125 Integer overflow in kernel KEVCVSS 3.1HIGH 8.4
  • TI-2013-01864 The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9… KEVCVSS 3.1HIGH 8.4
See all 21741 →

Sources