CVE-2026-98110

Description

A flaw was found in the Linux kernel's Intel Bluetooth driver. An attacker with a malicious or compromised Bluetooth device could exploit this vulnerability by providing a crafted response during firmware initialization that lacks a null terminator. Because the driver treats the firmware identifier as a null-terminated string rather than enforcing the advertised length boundary, it reads beyond the allocated memory buffer. This flaw can result in a Denial of Service (DoS) via a system crash or potentially expose sensitive kernel memory.

Statement

A low-impact out-of-bounds read flaw was found in the Linux kernel's Intel Bluetooth (btintel) driver as shipped in Red Hat Enterprise Linux 9 and 10, Red Hat In-Vehicle OS 2, and the RHEL CoreOS 9-based OpenShift Container Platform 4 and 5 streams. When parsing a firmware-version TLV response, the driver treats the firmware identifier as a NUL-terminated string without limiting the read to the advertised TLV length. A malicious or compromised Intel Bluetooth controller supplying a crafted response that lacks a NUL terminator can cause the kernel to read past the received buffer, which can crash the system (denial of service) and potentially expose adjacent kernel memory. Exploitation requires an attacker to attach or control the local Bluetooth controller hardware or its firmware; the flaw is not directly reachable from a remote Bluetooth peer. For this reason Red Hat assesses the impact as low, which differs from the Moderate severity suggested by the CVSS:3.1 base score of 5.5. Earlier RHEL 6, 7, and 8 kernels and earlier RHEL 9 and RHEL CoreOS streams are not affected because the vulnerable firmware-ID parsing code is not present there. Because the flaw is rated low impact, fixes for the affected streams are deferred to a future update; the residual risk is limited to denial of service or limited information exposure by an attacker who already controls the Bluetooth controller hardware.

Mitigation

Mitigation for this issue is either not available or the currently available options do not 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 Score5.57.1N/A
Attack VectorLocalLocalN/A
Attack ComplexityLowLowN/A
Privileges RequiredLowLowN/A
User InteractionNoneNoneN/A
ScopeUnchangedUnchangedN/A
ConfidentialityNoneHighN/A
Integrity ImpactNoneNoneN/A
Availability ImpactHighHighN/A

Vector

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

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.