Linux Kernel up to 7.2-rc2 Bluetooth bpa10x_setup out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k2.07

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.2-rc2. It has been classified as critical. This affects the function bpa10x_setup of the component Bluetooth. This manipulation causes out-of-bounds. This vulnerability is registered as CVE-2026-64549. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.2-rc2. It has been declared as critical. Affected by this vulnerability is the function bpa10x_setup of the component Bluetooth. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-64549 since 07/19/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/27/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc3 eliminates this vulnerability. Applying the patch 1813add71e386f77b3040e6c8dc9b7b3ff965a6c/bd56c23f1f8681a2857ee924a8bd3abf87c8913b/7a64f39ebe1bacd9004a62eceadac0b122ec3cc2/f80b4afe893dffa9fabdbf80fb4d6782b24a6793/4b4008dda1d0c6e598d7865631ad4eda63a560f0/bfc9e7be289df11e8e38c98cd78019d67fdd0bd5/a8e169d308775039200bb9c905c7ce420db6e8c5/dd068ef044128db655f48323a4acfd5907e04903 is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc3
Patch: 1813add71e386f77b3040e6c8dc9b7b3ff965a6c/bd56c23f1f8681a2857ee924a8bd3abf87c8913b/7a64f39ebe1bacd9004a62eceadac0b122ec3cc2/f80b4afe893dffa9fabdbf80fb4d6782b24a6793/4b4008dda1d0c6e598d7865631ad4eda63a560f0/bfc9e7be289df11e8e38c98cd78019d67fdd0bd5/a8e169d308775039200bb9c905c7ce420db6e8c5/dd068ef044128db655f48323a4acfd5907e04903

Timelineinfo

07/19/2026 CVE reserved
07/27/2026 +8 days Advisory disclosed
07/27/2026 +0 days VulDB entry created
07/27/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64549 (🔒)
GCVE (CVE): GCVE-0-2026-64549
GCVE (VulDB): GCVE-100-383605

Entryinfo

Created: 07/27/2026 23:24
Changes: 07/27/2026 23:24 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!