# CVE-2026-97907: Bluetooth: btrtl: Don't leak return code when parsing firmware format v2

> A flaw in the Linux kernel Bluetooth driver leaks uninitialized memory or previous return codes when parsing firmware, potentially exposing sensitive data.

- **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:** AZL-104846, BELL-CVE-2026-97907, DEBIAN-CVE-2026-97907, GHSA-cc6q-p4xg-qp8m, UBUNTU-CVE-2026-97907

## What is CVE-2026-97907?

CVE-2026-97907 is a 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: btrtl: Don't leak return code when parsing firmware format v2

When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally
ignores all security headers. However, the implementation simply breaks
from a switch statement and leaks uninitialized return code `rc' (if the
first section is a security one) or the previous section's `rc'.

Fix it by really skipping a loop with `continue'. For consistency and
readability, also do the same for the default case.

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


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

Apply the vendor's patch.

## Is CVE-2026-97907 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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