---
title: "CVE-2026-99239: Linux Kernel Bluetooth L2CAP - Race Condition"
description: "Linux kernel Bluetooth L2CAP contains a race condition caused by improper state checks and locking in __l2cap_chan_add and related functions, letting attackers cause inconsistent channel states, exploit requires concurrent operations."
url: https://panop.io/threat-heartbeat/CVE-2026-99239/
---

# CVE-2026-99239 Linux Kernel Bluetooth L2CAP - Race Condition

Linux kernel Bluetooth L2CAP contains a race condition caused by improper state checks and locking in \_\_l2cap\_chan\_add and related functions, letting attackers cause inconsistent channel states, exploit requires concurrent operations.

CVSS base score 7.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-99239)

## Details

Type

Race Condition

Impact

Denial Of Service

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Published

2 November 2026

Updated

3 November 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix for this race condition.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-99239](https://nvd.nist.gov/vuln/detail/CVE-2026-99239)
- [https://git.kernel.org/stable/c/73820561d8cbfd3364a29b8fa77f1707f26029da](https://git.kernel.org/stable/c/73820561d8cbfd3364a29b8fa77f1707f26029da)
- [https://git.kernel.org/stable/c/820579652b24ce277e0097cd65b42bd9b7b8bf07](https://git.kernel.org/stable/c/820579652b24ce277e0097cd65b42bd9b7b8bf07)
- [https://git.kernel.org/stable/c/85cc289eb08afa975375f838187369e68b429ee0](https://git.kernel.org/stable/c/85cc289eb08afa975375f838187369e68b429ee0)
- [https://git.kernel.org/stable/c/d3afd7803f9bc2a8c4270199497b60158b2fc647](https://git.kernel.org/stable/c/d3afd7803f9bc2a8c4270199497b60158b2fc647)
- [https://git.kernel.org/stable/c/e618d928ec7f88cbeadfa3542adcac40f474e629](https://git.kernel.org/stable/c/e618d928ec7f88cbeadfa3542adcac40f474e629)
- [https://git.kernel.org/stable/c/fabaff1c59ff2cc89cb7e5bd0186a5e15f0c73b2](https://git.kernel.org/stable/c/fabaff1c59ff2cc89cb7e5bd0186a5e15f0c73b2)
- [https://git.kernel.org/stable/c/10c705dd706aa93164ba41f2566f15206d6c178e](https://git.kernel.org/stable/c/10c705dd706aa93164ba41f2566f15206d6c178e)
- [https://git.kernel.org/stable/c/52fe88e4ef87311eee32b45c65603e7c69e75e7d](https://git.kernel.org/stable/c/52fe88e4ef87311eee32b45c65603e7c69e75e7d)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
