Linux Kernel up to 6.19.11 Bluetooth mesh_send adv_data[] buffer overflow

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.6$5k-$25k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Linux Kernel up to 6.1.167/6.6.133/6.12.80/6.18.21/6.19.11. This vulnerability affects the function mesh_send of the component Bluetooth. Performing a manipulation of the argument adv_data[] results in buffer overflow. This vulnerability was named CVE-2026-43017. The attack needs to be approached within the local network. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.1.167/6.6.133/6.12.80/6.18.21/6.19.11. This affects the function mesh_send of the component Bluetooth. The manipulation of the argument adv_data[] with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: validate mesh send advertising payload length mesh_send() currently bounds MGMT_OP_MESH_SEND by total command length, but it never verifies that the bytes supplied for the flexible adv_data[] array actually match the embedded adv_data_len field. MGMT_MESH_SEND_SIZE only covers the fixed header, so a truncated command can still pass the existing 20..50 byte range check and later drive the async mesh send path past the end of the queued command buffer. Keep rejecting zero-length and oversized advertising payloads, but validate adv_data_len explicitly and require the command length to exactly match the flexible array size before queueing the request.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-43017 since 05/01/2026. The exploitability is told to be easy. The attack needs to be initiated within the local network. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 05/01/2026).

Upgrading to version 6.1.168, 6.6.134, 6.12.81, 6.18.22 or 6.19.12 eliminates this vulnerability. Applying the patch 24fa32369cf15d8fc918bdfe94097b12e6acada0/244b639e6a3a8e26241e201004a3a9f764476631/0b706fb2294aff3adfd54653bda1b5e356ad4566/edb5898cfa91afe7e8f83eda18d93034c953d632/562ed1954f0c1bff3422b7b752bd3dacf185edbf/bda93eec78cdbfe5cda00785cefebd443e56b88b 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.

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: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Buffer overflow
CWE: CWE-120 / 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 6.1.168/6.6.134/6.12.81/6.18.22/6.19.12
Patch: 24fa32369cf15d8fc918bdfe94097b12e6acada0/244b639e6a3a8e26241e201004a3a9f764476631/0b706fb2294aff3adfd54653bda1b5e356ad4566/edb5898cfa91afe7e8f83eda18d93034c953d632/562ed1954f0c1bff3422b7b752bd3dacf185edbf/bda93eec78cdbfe5cda00785cefebd443e56b88b

Timelineinfo

05/01/2026 Advisory disclosed
05/01/2026 +0 days CVE reserved
05/01/2026 +0 days VulDB entry created
05/01/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-43017 (🔒)
GCVE (CVE): GCVE-0-2026-43017
GCVE (VulDB): GCVE-100-360693

Entryinfo

Created: 05/01/2026 17:58
Changes: 05/01/2026 17:58 (60)
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.

Want to know what is going to be exploited?

We predict KEV entries!