Bluetooth: MGMT: validate mesh send advertising payload length
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.168, 6.12.81, 6.18.22, 6.19.12, 6.6.134
- CVEs
- CVE-2026-43017
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 23:22 UTC · Revision 1
Source evidence
Bluetooth: MGMT: validate mesh send advertising payload length
core-osv · Original sourcePublished 1 May 2026, 14:15 UTC
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.
osv:CVE-2026-43017
Kernel
Fixed versions: 6.1.168, 6.6.134, 6.12.81, 6.18.22, 6.19.12
Complete source record
{
"id": "85aff60d8a82392fa2a65c49ab51ad09378640b2d56563f75fc4f2bfa6e77813",
"url": "https://osv.dev/vulnerability/CVE-2026-43017",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Bluetooth: MGMT: validate mesh send advertising payload length",
"summary": "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.",
"evidence": "osv:CVE-2026-43017",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.168",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.134",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.81",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.22",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.12",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-43017",
"aliases": [
"CVE-2026-43017"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "b338d91703fae6f6afd67f3f75caa3b8f36ddef3"
},
{
"fixed": "24fa32369cf15d8fc918bdfe94097b12e6acada0"
},
{
"fixed": "244b639e6a3a8e26241e201004a3a9f764476631"
},
{
"fixed": "0b706fb2294aff3adfd54653bda1b5e356ad4566"
},
{
"fixed": "edb5898cfa91afe7e8f83eda18d93034c953d632"
},
{
"fixed": "562ed1954f0c1bff3422b7b752bd3dacf185edbf"
},
{
"fixed": "bda93eec78cdbfe5cda00785cefebd443e56b88b"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43017.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.1.0"
},
{
"fixed": "6.1.168"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.134"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.81"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.22"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.12"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43017.json"
}
}
],
"modified": "2026-10-28T02:30:24.389790963Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0b706fb2294aff3adfd54653bda1b5e356ad4566",
"https://git.kernel.org/stable/c/244b639e6a3a8e26241e201004a3a9f764476631",
"https://git.kernel.org/stable/c/24fa32369cf15d8fc918bdfe94097b12e6acada0",
"https://git.kernel.org/stable/c/562ed1954f0c1bff3422b7b752bd3dacf185edbf",
"https://git.kernel.org/stable/c/bda93eec78cdbfe5cda00785cefebd443e56b88b",
"https://git.kernel.org/stable/c/edb5898cfa91afe7e8f83eda18d93034c953d632",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43017.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-43017",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43017.json"
}
},
"related_cves": [
{
"value": "CVE-2026-43017",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 490845,
"published_at": "2026-05-01T14:15:21.561+00:00"
}