CVE-2026-64549

Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup()

N/A
Published: July 27, 2026 at 08:10 PM UTC
Updated: August 17, 2026 at 05:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.4 ≤ v < 5.10.2614.4 ≤ v < 5.15.2124.4 ≤ v < 6.1.1784.4 ≤ v < 6.12.974.4 ≤ v < 6.18.404.4 ≤ v < 6.6.1454.4 ≤ v < 7.1.54.4 ≤ v < 7.24.4ddd68ec8f4847b460c9f580076eafe13b031a6fd
Vendor states this is fixed in 1813add71e386f77b3040e6c8dc9b7b3ff965a6c (fixed)
Vendor states this is fixed in 4b4008dda1d0c6e598d7865631ad4eda63a560f0 (fixed)
Vendor states this is fixed in 7a64f39ebe1bacd9004a62eceadac0b122ec3cc2 (fixed)
Vendor states this is fixed in a8e169d308775039200bb9c905c7ce420db6e8c5 (fixed)
Vendor states this is fixed in bd56c23f1f8681a2857ee924a8bd3abf87c8913b (fixed)
Vendor states this is fixed in bfc9e7be289df11e8e38c98cd78019d67fdd0bd5 (fixed)
Vendor states this is fixed in dd068ef044128db655f48323a4acfd5907e04903 (fixed)
Vendor states this is fixed in f80b4afe893dffa9fabdbf80fb4d6782b24a6793 (fixed)
Vendor states this is fixed in 4.4 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card