CVE-2026-98110

Awaiting Analysis Awaiting Analysis - Queue

Bluetooth Firmware ID Buffer Overflow in Linux Kernel

Publication date: 2026-09-25

Last updated on: 2026-09-30

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btintel: bound firmware ID by TLV length The firmware ID is treated as a NUL-terminated string even though the TLV length is its only boundary. If the value does not contain a NUL terminator, snprintf() can read beyond the received response. Limit the conversion to the advertised TLV value length.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-25

Last Modified

2026-09-30

Generated

2026-10-16

AI Q&A

2026-09-25

EPSS Evaluated

2026-10-14

NVD

CVE-2026-98110

EUVD

EUVD-2026-86941

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability is in the Linux kernel's Bluetooth subsystem. It involves the btintel driver improperly handling firmware ID strings. The driver assumes the firmware ID is a NUL-terminated string but only uses the TLV length as a boundary. If the firmware ID lacks a NUL terminator, the snprintf function may read beyond the intended data, potentially exposing memory.

Detection Guidance

This vulnerability is specific to the Linux kernel's Bluetooth subsystem and may not have direct detection commands. Check if your system uses an affected kernel version and inspect Bluetooth firmware handling logs for anomalies.

Impact Analysis

This vulnerability could allow an attacker to read sensitive memory contents or cause a system crash by exploiting the buffer over-read. It primarily affects systems using Bluetooth with Intel hardware and the Linux kernel.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards as it is a low-level Bluetooth firmware issue in the Linux kernel. Compliance risks would only arise if exploitation led to unauthorized data access or system compromise, which is not specified in the provided context.

Mitigation Strategies

Update your Linux kernel to the latest patched version. Monitor vendor advisories for firmware updates. Disable Bluetooth if not in use or restrict its usage to trusted environments.

Hi! I’m here to help you understand CVE-2026-98110. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70