Description
In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: btintel_pcie: validate device-supplied DMA indices

In btintel_pcie_msix_rx_handle(), the driver processes RX completion
descriptors (urbd1) written by the PCIe device into DMA-coherent memory.
urbd1->frbd_tag (a 16-bit field fully controlled by the device firmware
via DMA) is used directly as an array index into rxq->bufs[] without any
bounds check. rxq->bufs[] has only BTINTEL_PCIE_RX_DESCS_COUNT (64)
entries, while frbd_tag can be any value 0-65535. A malicious or
malfunctioning device can write an out-of-range frbd_tag, causing the
driver to dereference an out-of-bounds data_buf pointer.

Additionally, cr_hia is read from a DMA-shared index array also writable
by the device; if the device sets cr_hia >= rxq->count, the while-loop
never terminates because cr_tia is wrapped via modulo rxq->count and can
never equal an out-of-range cr_hia.

Add bounds validation for cr_hia and frbd_tag in the RX path, and cr_hia
in the TX path. Log invalid values with bt_dev_err before returning.
Published: 2026-10-18
Score: n/a
EPSS: n/a
KEV: No
Impact: Out‑of‑bounds memory access in the Linux kernel Bluetooth driver can lead to a kernel crash or privilege escalation.
Action: Update Kernel
AI Analysis

Impact

The vulnerability occurs in the btintel_pcie driver when it processes device‑supplied DMA descriptors. A 16‑bit field controlled by the PCIe device, frbd_tag, is used as an array index with no bounds checking. The driver array has only 64 entries, while the field can take any value up to 65535, allowing an attacker to dereference an out‑of‑bounds pointer and corrupt kernel memory. Additionally, the driver can enter an infinite loop if the device supplies a cr_hia value that is out of range, which may further destabilize the system.

Affected Systems

The flaw affects the Linux kernel’s Bluetooth implementation on all mainstream distributions that compile the btintel_pcie driver. No specific version numbers are listed, so any kernel build that includes this driver prior to the fix is potentially vulnerable.

Risk and Exploitability

Because the driver runs in kernel space, successful exploitation can lead to arbitrary code execution with root privileges. The EPSS score is not available and the flaw is not listed in CISA’s KEV catalog, but kernel vulnerabilities with unchecked array indices are typically considered high‑risk. Attackers would need physical or firmware‑level control over a PCIe Bluetooth device to supply malicious DMA indices, a scenario that is realistic for compromised hardware or attacks on embedded systems with Bluetooth connectivity.

Generated by OpenCVE AI on October 18, 2026 at 22:44 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a release that includes the bounds‑checking fix for btintel_pcie.
  • If immediate kernel upgrade is not possible, restrict the set of PCIe devices that can use the Bluetooth driver to trusted hardware only.
  • Continuously monitor kernel logs for btintel_pcie‑related errors or crashes, and investigate any abnormal kernel panics promptly.

Generated by OpenCVE AI on October 18, 2026 at 22:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 18 Oct 2026 23:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-129

Sun, 18 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btintel_pcie: validate device-supplied DMA indices In btintel_pcie_msix_rx_handle(), the driver processes RX completion descriptors (urbd1) written by the PCIe device into DMA-coherent memory. urbd1->frbd_tag (a 16-bit field fully controlled by the device firmware via DMA) is used directly as an array index into rxq->bufs[] without any bounds check. rxq->bufs[] has only BTINTEL_PCIE_RX_DESCS_COUNT (64) entries, while frbd_tag can be any value 0-65535. A malicious or malfunctioning device can write an out-of-range frbd_tag, causing the driver to dereference an out-of-bounds data_buf pointer. Additionally, cr_hia is read from a DMA-shared index array also writable by the device; if the device sets cr_hia >= rxq->count, the while-loop never terminates because cr_tia is wrapped via modulo rxq->count and can never equal an out-of-range cr_hia. Add bounds validation for cr_hia and frbd_tag in the RX path, and cr_hia in the TX path. Log invalid values with bt_dev_err before returning.
Title Bluetooth: btintel_pcie: validate device-supplied DMA indices
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-18T15:19:13.760Z

Reserved: 2026-09-25T10:25:14.359Z

Link: CVE-2026-98601

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T16:17:12.817

Modified: 2026-10-18T16:17:12.817

Link: CVE-2026-98601

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-18T22:45:04Z

Weaknesses
  • CWE-129

    Improper Validation of Array Index