CVE-2026-99012

Description

A flaw was found in the Linux kernel's Bluetooth subsystem. A local attacker can cause a Denial of Service (DoS) by issuing concurrent connection requests on Bluetooth isochronous (ISO) sockets. Due to improper locking and lack of serialization during connection establishment, simultaneous connect calls can race against each other and trigger a use-after-free memory error, leading to a system crash.

Statement

A race between concurrent Bluetooth ISO connect calls can replace iso_pi sk conn while an older CIS or BIS connection still retains its conn sk back pointer. Later asynchronous teardown can call iso_sock_hold through the stale connection after the socket has been released, producing a KASAN confirmed slab use after free. For the CVSS the PR:L reflects that an attacker needs local code execution and access to a Bluetooth ISO socket and the same socket descriptor must be used by concurrent callers. AC:H reflects the required race between connect, attachment, socket release, and an asynchronous HCI callback. The confirmed UAF can crash the kernel and may affect reclaimed slab memory, but reliable privilege escalation depends on controlled object reuse and is not demonstrated.

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.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.7N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.