# CVE-2026-98291: Bluetooth: btintel_pcie: fix off-by-one bounds check in RX submit

> An off-by-one error in the Linux kernel Bluetooth driver allows out-of-bounds memory access, potentially leading to system crashes or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98291, DEBIAN-CVE-2026-98291, GHSA-7r69-vgp4-2564, UBUNTU-CVE-2026-98291

## What is CVE-2026-98291?

CVE-2026-98291 is a vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Bluetooth: btintel_pcie: fix off-by-one bounds check in RX submit

btintel_pcie_submit_rx() used frbd_index > rxq->count to guard the
FRBD array access, allowing frbd_index == rxq->count to pass through
and index one element past the end of the array. Change the check to
>= rxq->count so every out-of-range index is rejected.

This issue was reported by Claude Mythos.

## Which versions are affected by CVE-2026-98291?


## How do I fix CVE-2026-98291?

Apply the vendor's patch.

## Is CVE-2026-98291 being exploited?

There is no known exploitation of CVE-2026-98291 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98291 and fix it if it is affected.

What it is: CVE-2026-98291 is a vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98291 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98291/ (Markdown: https://insights.sbomify.com/CVE-2026-98291/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98291
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98291
- OSV: https://osv.dev/vulnerability/CVE-2026-98291

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98291/
Summaries are generated and may contain mistakes; the official description above is the record.