Linux Kernel up to 7.0.12 Bluetooth tlv_data_is_valid length 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.
2.5$0-$5k1.25-

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 7.0.12. This affects the function tlv_data_is_valid of the component Bluetooth. The manipulation of the argument length results in out-of-bounds. This vulnerability was named CVE-2026-53255. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 7.0.12. Affected is the function tlv_data_is_valid of the component Bluetooth. The manipulation of the argument length with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: validate advertising TLV before type checks tlv_data_is_valid() reads each advertising data field length from data[i], then inspects data[i + 1] for managed EIR types before checking that the current field still fits inside the supplied buffer. A malformed field whose length byte is the last byte of the buffer can therefore make the parser read one byte past the advertising data. KASAN reported the following when a malformed MGMT_OP_ADD_ADVERTISING request reached that path: BUG: KASAN: vmalloc-out-of-bounds in tlv_data_is_valid() Read of size 1 Call trace: tlv_data_is_valid() add_advertising() hci_mgmt_cmd() hci_sock_sendmsg() Move the existing element-length check before any type-octet inspection so each non-empty element is proven to contain its type byte before the parser looks at data[i + 1].

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-53255 since 06/09/2026. The exploitability is told to be difficult. There are known technical details, but no exploit is available.

Upgrading to version 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36 or 7.0.13 eliminates this vulnerability. Applying the patch 13ad995071a06570668dd8daab3616c247c72080/06fcbd79c3c360a50f9be9d370769bbd738d0976/f7093ac233c1e7f51d125534f46067772a113175/74c08e4db35a476c3462aeb65846f955be732626/18fea1cb0c2599752e908c8217490f73ddd33e00/1a3c8ffbb469859b076445af44bdfa6a711d483e/2a3f3ed9e198ae23c15859ace2f9ca6cfdc35b57/de23fb62259aa01d294f77238ae3b835eb674413 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.6
VulDB Meta Temp Score: 2.5

VulDB Base Score: 2.6
VulDB Temp Score: 2.5
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: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

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.259/5.15.210/6.1.176/6.6.143/6.12.94/6.18.36/7.0.13
Patch: 13ad995071a06570668dd8daab3616c247c72080/06fcbd79c3c360a50f9be9d370769bbd738d0976/f7093ac233c1e7f51d125534f46067772a113175/74c08e4db35a476c3462aeb65846f955be732626/18fea1cb0c2599752e908c8217490f73ddd33e00/1a3c8ffbb469859b076445af44bdfa6a711d483e/2a3f3ed9e198ae23c15859ace2f9ca6cfdc35b57/de23fb62259aa01d294f77238ae3b835eb674413

Timelineinfo

06/09/2026 CVE reserved
06/25/2026 +16 days Advisory disclosed
06/25/2026 +0 days VulDB entry created
06/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-53255 (🔒)
GCVE (CVE): GCVE-0-2026-53255
GCVE (VulDB): GCVE-100-373788

Entryinfo

Created: 06/25/2026 12:23
Changes: 06/25/2026 12:23 (60)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!