# CVE-2026-64549: Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup()

> A malicious Bluetooth device can trigger an out-of-bounds read in the Linux kernel, leaking adjacent memory contents into logs and debugfs.

- **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:** 27 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** AZL-94074, BELL-CVE-2026-64549, DEBIAN-CVE-2026-64549, GHSA-4pq4-7m8r-frpc, UBUNTU-CVE-2026-64549

## What is CVE-2026-64549?

CVE-2026-64549 is a vulnerability in Linux, published on 27 Jul 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: bpa10x: avoid OOB read of revision string in bpa10x_setup()

bpa10x_setup() sends the vendor command 0xfc0e and passes the response
to bt_dev_info() and hci_set_fw_info() as a "%s" string starting at
skb->data + 1, without checking the length:

	bt_dev_info(hdev, "%s", (char *)(skb->data + 1));
	hci_set_fw_info(hdev, "%s", skb->data + 1);

A device that returns a one-byte response (status only) leaves
skb->data + 1 past the end of the data, and the %s walk reads adjacent
slab memory until it meets a NUL. The same happens when the payload is
not NUL-terminated within skb->len. The out-of-bounds bytes end up in
the kernel log and the firmware-info debugfs file.

Print the revision string with a bounded "%.*s" limited to skb->len - 1
instead. This keeps the string readable for well-behaved devices while
never reading past the received data, and does not fail setup, so a
device returning a short or unterminated response keeps working.

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


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

Apply the vendor's patch.

## Is CVE-2026-64549 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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