# CVE-2026-97976: Bluetooth: btintel_pcie: validate packet_len before skb_put_data

> An out-of-bounds read in the Linux kernel Bluetooth Intel PCIe driver allows attackers with local access or malicious firmware to cause crashes or leak memory.

- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-97976, DEBIAN-CVE-2026-97976, GHSA-wxpf-g955-mjcc, UBUNTU-CVE-2026-97976

## What is CVE-2026-97976?

CVE-2026-97976 is a memory corruption vulnerability in Linux, published on 25 Sep 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 packet_len before skb_put_data

btintel_pcie_submit_rx_work() reads packet_len from rfh_hdr without
checking if it exceeds the RX buffer size. An oversized packet_len
can lead to an out-of-bounds read in skb_put_data().

Validate packet_len to ensure it is non-zero and does not exceed
BTINTEL_PCIE_BUFFER_SIZE - sizeof(*rfh_hdr), logging an error when
invalid.

This issue was reported by Claude Mythos. It can be simulated either by
using customized firmware configured to return an invalid packet_len or
by modifying rfh_hdr->packet_len in the driver before calling
btintel_pcie_submit_rx_work().

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


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

Apply the vendor's patch.

## Is CVE-2026-97976 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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