CVE-2026-99481

Description

A flaw was found in the Linux kernel's Bluetooth virtual Host Controller Interface (HCI) driver. This issue may allow a local user to cause a Denial of Service (DoS) through a system crash. The vulnerability occurs because certain debug file operations do not properly register module ownership, allowing the driver module to be unloaded while its files remain open. When the user subsequently closes the open file descriptor, the kernel attempts to access unmapped memory, resulting in a kernel crash.

Statement

This vulnerability is rated as Moderate impact because exploitation requires local administrative access to debugfs interfaces and permissions to unload kernel modules, limiting the blast radius to a local denial of service. In default Red Hat Enterprise Linux environments, the virtual Bluetooth HCI driver is built as an optional kernel module that is not loaded unless virtual Bluetooth devices are explicitly configured. Because triggering the kernel crash requires elevated privileges (such as CAP_SYS_MODULE) that already possess high system authority, the risk to unprivileged users is minimal.

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.4N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.