cve.bz

CVE-2026-99239 linux linux

7.8 highEPSS 0.1%Fix available

High (7.8) in linux linux. EPSS 0.1% 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: refuse __l2cap_chan_add if chan already has conn l2cap_chan may be linked to l2cap_conn at most once. This is assumed in several places, eg l2cap_chan_del cleanup. There is a TOCTOU race where the invariant is violated: [Task 1] [Task 2] l2cap_chan_connect l2cap_sock_bind l2cap_chan_lock lock_sock l2cap_state_change if (sk->sk_state != BT_OPEN) chan->state = BT_CONNECT l2cap_sock_state_change_cb chan->state = BT_BOUND sk->sk_state = BT_BOUND lock_sock <------------------ release_sock sk->sk_state = BT_CONNECT l2cap_sock_connect() does not check sk->sk_state, so since chan->state is now BT_BOUND, subsequent connect() ends up with second __l2cap_chan_add. Explicitly document and check the invariant in __l2cap_chan_add with WARN_ON_ONCE. The only callsite where it could be hit is l2cap_chan_connect, so add pre-check there to avoid relying on chan->state. chan->state read/write is not properly guarded currently so there can be other TOCTOUC problems. Add l2cap_lock_chan in l2cap_sock_bind() to guard chan->state write.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 2nd 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 5.10.273
  • Linux Linux: fixed in 5.15.224
  • Linux Linux: fixed in 6.1.191
  • Linux Linux: fixed in 6.6.161
  • Linux Linux: fixed in 6.12.115
  • Linux Linux: fixed in 6.18.60
  • Linux Linux: fixed in 7.2.14
  • Linux Linux: fixed in 7.3.1
  • Debian, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-99239 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99239?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99239?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-99239 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.

Badge for a README or a site

CVE-2026-99239

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-99239](https://cve.bz/cve/badge/CVE-2026-99239.svg)](https://cve.bz/cve/CVE-2026-99239)

HTML:

<a href="https://cve.bz/cve/CVE-2026-99239"><img src="https://cve.bz/cve/badge/CVE-2026-99239.svg" alt="CVE-2026-99239"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 5.10.265 before 5.10.273
Linuxfrom 5.15.216 before 5.15.224
Linuxfrom 6.1.183 before 6.1.191
Linuxfrom 6.6.145 before 6.6.161
Linuxfrom 6.12.97 before 6.12.115
Linuxfrom 6.18.39 before 6.18.60
Linuxfrom 7.1.4 before 7.2
Linux7.2 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.273
Linux5.155.15.224
Linux6.16.1.191
Linux6.66.6.161
Linux6.126.12.115
Linux6.186.18.60
Linux7.27.2.14
Linux7.37.3.1
Linuxlater releases7.4-rc1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-99239
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-99239
Debian13linux6.12.115-1DEBIAN-CVE-2026-99239
Debian14linux7.2.14-1DEBIAN-CVE-2026-99239
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99239
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99239
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99239
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 57 moreno fix listedUBUNTU-CVE-2026-99239
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 48 moreno fix listedUBUNTU-CVE-2026-99239
Ubuntu26.04:LTSlinux, linux-aws, linux-gcp and 12 moreno fix listedUBUNTU-CVE-2026-99239
Ubuntu26.10linux, linux-aws, linux-gcp and 6 moreno fix listedUBUNTU-CVE-2026-99239
UbuntuNvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-99239
UbuntuPro:20.04:LTSlinux-aws-5.15, linux-gcp-5.15, linux-hwe-5.15 and 8 moreno fix listedUBUNTU-CVE-2026-99239
UbuntuPro:FIPS-updates:22.04:LTS, Pro:FIPS-updates:24.04:LTSlinux-fips, linux-aws-fips, linux-gcp-fips and 1 moreno fix listedUBUNTU-CVE-2026-99239
UbuntuPro:Realtime:22.04:LTSlinux-realtime, linux-realtime-6.8, linux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-99239
UbuntuPro:Realtime:24.04:LTSlinux-realtime, linux-realtime-6.14, linux-realtime-6.17 and 1 moreno fix listedUBUNTU-CVE-2026-99239
openSUSETumbleweedkernel-source7.3.3-1.1openSUSE-SU-2026:12497-1
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-99239
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-99239
Alpaquitastreamlinux-lts6.18.62-r0BELL-CVE-2026-99239

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; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because an unprivileged local user can exploit the concurrent socket handling flaw to corrupt kernel memory and potentially elevate privileges on systems with Bluetooth enabled. Although exploitation requires local system access, standard unprivileged user accounts can create the required Bluetooth sockets without elevated permissions, enabling complete host compromise. Enterprise installations lacking physical Bluetooth hardware or with the Bluetooth kernel module disabled or omitted are not exposed to this risk.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-11-04) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to synchronize Bluetooth L2CAP socket bind and connect state updates with channel locking to prevent duplicate channel attachments: upgrade to the corresponding fixed Red Hat builds, which acquire l2cap_chan_lock in l2cap_sock_bind to guard chan->state updates, reject connection attempts in l2cap_chan_connect if chan->conn or FLAG_DEL is set, and refuse __l2cap_chan_add when chan already has an associated conn, closing all 2 injection vectors (concurrent l2cap_sock_bind and l2cap_chan_connect system calls, interleaved socket state modification via multi-threaded Bluetooth socket operations). Until patched, this is only a concern on Linux systems with the Bluetooth subsystem enabled and local unprivileged user access — Systems lacking physical Bluetooth hardware or with the Bluetooth kernel module disabled or omitted are unaffected — so disable or unload the Bluetooth kernel module on hosts where Bluetooth is not required, and restrict unprivileged local users from creating Bluetooth sockets. As a compensating measure, enforce SELinux to restrict confined process domains from creating or interacting with Bluetooth L2CAP sockets, map local users to confined SELinux roles to deny permissions to instantiate raw Bluetooth socket families, deploy EDR agents to detect anomalous privilege escalation behaviors and post-exploit payload execution, use Falco or eBPF runtime security to monitor kernel system call patterns and flag unexpected privilege transitions, enable KASAN or HWASan instrumentation to detect kernel memory corruption and invalid channel pointer reuse, and enable KASLR to randomize kernel code addresses and hinder control-flow redirection during memory corruption. These controls limit blast radius and contain exploitation, but they do not fix the underlying TOCTOU race condition defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
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 9kernelNot affected
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-10Not 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-99239.

References

Check your stackJSON