Answer in brief
CVE-2026-98601 records a Unknown severity vulnerability in Bluetooth: btintel_pcie: validate device-supplied DMA indices. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c2b636b3f788d10486a6691ad6dd3ec4c93bd78e <f42cd95e679d5b78611cd2208cd1c41ad0045ffa || >=c2b636b3f788d10486a6691ad6dd3ec4c93bd78e <8ec5838a35b03ac0cf3602452a369898051ffaf9 || >=c2b636b3f788d10486a6691ad6dd3ec4c93bd78e <b29b70bfa12133423924fcd0327c19a802f7e368 || >=c2b636b3f788d10486a6691ad6dd3ec4c93bd78e <37a11129345337efd6eef8e62b03b6348cd0dd8b | f42cd95e679d5b78611cd2208cd1c41ad0045ffa, 8ec5838a35b03ac0cf3602452a369898051ffaf9, b29b70bfa12133423924fcd0327c19a802f7e368, 37a11129345337efd6eef8e62b03b6348cd0dd8b |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.