cve.bz

CVE-2026-90092 linux linux

8.0 highEPSS 0.4%Fix available

High (8.0) in linux linux. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.0 high
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.1.188
  • Linux Linux: fixed in 6.6.157
  • Linux Linux: fixed in 6.12.110
  • Linux Linux: fixed in 6.18.52
  • Linux Linux: fixed in 7.2.6
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, SUSE, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-90092 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-90092?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-90092?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-90092 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 6.1.175 before 6.1.188
Linuxfrom 6.6.140 before 6.6.157
Linuxfrom 6.12.88 before 6.12.110
Linuxfrom 6.18.30 before 6.18.52
Linuxfrom 5.10.258 before 5.11
Linuxfrom 5.15.209 before 5.16
Linuxfrom 7.0.7 before 7.1
Linux7.1 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.188
Linux6.66.6.157
Linux6.126.12.110
Linux6.186.18.52
Linux7.27.2.6
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.190-1DEBIAN-CVE-2026-90092
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-90092
Debian13linux6.12.111-1DEBIAN-CVE-2026-90092
Debian14linux7.2.6-1DEBIAN-CVE-2026-90092
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-90092
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-90092
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-90092
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 48 moreno fix listedUBUNTU-CVE-2026-90092
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-90092 USN-9024-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-90092 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-90092 USN-9026-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-90092 USN-9024-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-90092 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1069.70~22.04.1UBUNTU-CVE-2026-90092 USN-9024-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-149.149.1~22.04.1UBUNTU-CVE-2026-90092 USN-9024-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-90092 USN-9025-1
47 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.90.1SUSE-SU-2026:5091-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.41.1SUSE-SU-2026:24651-1
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.339.1SUSE-SU-2026:5121-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_901-8.3.1SUSE-SU-2026:5121-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_241-150700.15.3.1SUSE-SU-2026:5091-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.90.1SUSE-SU-2026:5091-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.90.1.150700.17.51.1SUSE-SU-2026:5091-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.90.1SUSE-SU-2026:5091-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure6.4.0-150700.53.90.1SUSE-SU-2026:5091-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5kernel-syms, kernel-source, kernel-default4.12.14-122.339.1SUSE-SU-2026:5121-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.41.1SUSE-SU-2026:24662-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.41.1.160000.2.32SUSE-SU-2026:24662-1
8 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.41.1.160000.2.31openSUSE-SU-2026:22266-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.41.1openSUSE-SU-2026:22266-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia6.12.0-160100.7.1openSUSE-SU-2026:22307-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
openSUSETumbleweedkernel-source7.2.7-1.1openSUSE-SU-2026:11880-1
Azure Linux3kernel6.6.157.1-1AZL-102993
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-90092
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-90092
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-90092

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A race in the Bluetooth L2CAP socket path can allow l2cap_sock_new_connection_cb to add a new child socket after the parent listener has completed teardown and entered BT_CLOSED. The child socket may retain a dangling parent reference, and later dereferencing that reference can result in use after free and a kernel crash. A nearby Bluetooth peer may be able to trigger the race by initiating an L2CAP connection while the listening socket is being closed. For the CVSS the PR:N value is used because no account or local privileges on the target are required when the attacker can directly reach the exposed Bluetooth L2CAP service. AV:A is used because exploitation requires Bluetooth proximity or equivalent adjacent radio access rather than general Internet reachability. AC:H reflects the timing dependent race between connection creation and listener teardown. Impact is at least denial of service through a kernel crash. In the worst still defensible case, reuse of the freed socket object may affect confidentiality and integrity or potentially support privilege escalation, although a reliable arbitrary read or write primitive is not demonstrated.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-90092.

References

Check your stackJSON