CVE-2026-64549
Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup()
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.
INFO
Published Date :
July 27, 2026, 9:17 p.m.
Last Modified :
July 27, 2026, 9:17 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64549
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Apply the provided patch to the Linux kernel.
- Limit string length using "%.*s" in bpa10x_setup().
- Ensure firmware info strings are NUL-terminated.
- Update the Bluetooth driver to the latest version.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64549.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64549 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64549
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64549 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64549 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 27, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'ddd68ec8f4847b460c9f580076eafe13b031a6fd', 'lessThan': '1813add71e386f77b3040e6c8dc9b7b3ff965a6c', 'versionType': 'git'}, {'status': 'affected', 'version': 'ddd68ec8f4847b460c9f580076eafe13b031a6fd', 'lessThan': 'bd56c23f1f8681a2857ee924a8bd3abf87c8913b', 'versionType': 'git'}, {'status': 'affected', 'version': 'ddd68ec8f4847b460c9f580076eafe13b031a6fd', 'lessThan': '7a64f39ebe1bacd9004a62eceadac0b122ec3cc2', 'versionType': 'git'}, {'status': 'affected', 'version': 'ddd68ec8f4847b460c9f580076eafe13b031a6fd', 'lessThan': 'f80b4afe893dffa9fabdbf80fb4d6782b24a6793', 'versionType': 'git'}, {'status': 'affected', 'version': 'ddd68ec8f4847b460c9f580076eafe13b031a6fd', 'lessThan': '4b4008dda1d0c6e598d7865631ad4eda63a560f0', 'versionType': 'git'}, {'status': 'affected', 'version': 'ddd68ec8f4847b460c9f580076eafe13b031a6fd', 'lessThan': 'bfc9e7be289df11e8e38c98cd78019d67fdd0bd5', 'versionType': 'git'}, {'status': 'affected', 'version': 'ddd68ec8f4847b460c9f580076eafe13b031a6fd', 'lessThan': 'a8e169d308775039200bb9c905c7ce420db6e8c5', 'versionType': 'git'}, {'status': 'affected', 'version': 'ddd68ec8f4847b460c9f580076eafe13b031a6fd', 'lessThan': 'dd068ef044128db655f48323a4acfd5907e04903', 'versionType': 'git'}], 'programFiles': ['drivers/bluetooth/bpa10x.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4.4'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.4', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.261', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.97', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.40', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.5', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc3', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/bluetooth/bpa10x.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/1813add71e386f77b3040e6c8dc9b7b3ff965a6c Added Reference https://git.kernel.org/stable/c/4b4008dda1d0c6e598d7865631ad4eda63a560f0 Added Reference https://git.kernel.org/stable/c/7a64f39ebe1bacd9004a62eceadac0b122ec3cc2 Added Reference https://git.kernel.org/stable/c/a8e169d308775039200bb9c905c7ce420db6e8c5 Added Reference https://git.kernel.org/stable/c/bd56c23f1f8681a2857ee924a8bd3abf87c8913b Added Reference https://git.kernel.org/stable/c/bfc9e7be289df11e8e38c98cd78019d67fdd0bd5 Added Reference https://git.kernel.org/stable/c/dd068ef044128db655f48323a4acfd5907e04903 Added Reference https://git.kernel.org/stable/c/f80b4afe893dffa9fabdbf80fb4d6782b24a6793