# CVE-2026-98730: Bluetooth: btintel_pcie: reject oversized TX packets in send_frame()

> A local attacker with HCI access can overflow a kernel buffer via oversized Bluetooth packets, potentially leading to code execution or privilege escalation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98730, DEBIAN-CVE-2026-98730, GHSA-3249-w698-6rq3, UBUNTU-CVE-2026-98730

## What is CVE-2026-98730?

CVE-2026-98730 is a memory corruption vulnerability in Linux, published on 18 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: reject oversized TX packets in send_frame()

btintel_pcie_send_frame() eventually copies skb->data into a fixed
BTINTEL_PCIE_BUFFER_SIZE (4096) DMA buffer via memcpy() in
btintel_pcie_prepare_tx(), with a 4-byte PCIe type header prepended.
A user-space process with HCI_CHANNEL_USER access can inject an
oversized packet and overflow the buffer.

Reject packets larger than
BTINTEL_PCIE_BUFFER_SIZE - BTINTEL_PCIE_HCI_TYPE_LEN on entry.

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


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

Apply the vendor's patch.

## Is CVE-2026-98730 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98730 is a memory corruption vulnerability in Linux, published on 18 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-98730 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-98730/ (Markdown: https://insights.sbomify.com/CVE-2026-98730/index.md)
```

## Sources

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

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