# CVE-2026-98296: Bluetooth: btintel_pcie: validate TX skb length in send_sync

> A missing bounds check in the Linux kernel's Intel PCIe Bluetooth driver allows buffer overflows, potentially leading to code execution or system crashes.

- **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-98296, DEBIAN-CVE-2026-98296, GHSA-hx9c-7jvw-48j5, UBUNTU-CVE-2026-98296

## What is CVE-2026-98296?

CVE-2026-98296 is a memory corruption 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: validate TX skb length in send_sync

btintel_pcie_prepare_tx() copies skb->len bytes into a fixed
BTINTEL_PCIE_BUFFER_SIZE (4096) DMA slot via an unchecked memcpy.
Oversized packets are currently rejected only in
btintel_pcie_send_frame(); any future caller of
btintel_pcie_send_sync() would silently overflow the DMA buffer.

Add the bounds check in btintel_pcie_send_sync() itself, right
before skb_push() and the DMA copy.

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


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

Apply the vendor's patch.

## Is CVE-2026-98296 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98296 is a memory corruption 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-98296 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-98296/ (Markdown: https://insights.sbomify.com/CVE-2026-98296/index.md)
```

## Sources

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

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