CVE-2026-98733

Description

A flaw was found in the Linux kernel's Bluetooth subsystem. Inadequate synchronization when handling fragmented isochronous (ISO) data packets allows a race condition between packet queueing and transmission operations. A local user could exploit this flaw to trigger a use-after-free condition, leading to a system crash and Denial of Service (DoS).

Statement

A race in the Bluetooth HCI ISO fragmented transmit path allows hci_queue_iso to update the packet queue without holding its lock while the transmit worker can dequeue and release the previous tail SKB. If the driver frees that SKB before insertion resumes, __skb_queue_tail can write through the stale tail pointer and cause a slab use after free or corrupt the queue. A local process can reach the affected path through iso_sock_sendmsg when fragmented ISO packets are queued while transmission is active. For the CVSS the PR:L value is selected because local code execution and access to a Bluetooth ISO socket are required, while full administrative privileges are not clearly required by the affected send path. AC:H reflects the timing dependent race between packet insertion, dequeue, and driver release. The issue is not directly network reachable because a remote Bluetooth peer cannot by itself invoke the local sendmsg path based on the available evidence. Impact is at least a local denial of service through a kernel crash and may include confidentiality or integrity impact because the stale pointer is used for a write into freed slab memory. The paranoid score uses C:H I:H A:H because a confirmed write use after free can potentially support privilege escalation if object reuse and race timing become controllable, but that escalation path 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 Score7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/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.