Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43017Bluetooth: MGMT: validate mesh send advertising payload length

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43017, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 24fa32369cf15d8fc918bdfe94097b12e6acada0
    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 244b639e6a3a8e26241e201004a3a9f764476631
    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 0b706fb2294aff3adfd54653bda1b5e356ad4566
    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < edb5898cfa91afe7e8f83eda18d93034c953d632
    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 562ed1954f0c1bff3422b7b752bd3dacf185edbf
    • affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < bda93eec78cdbfe5cda00785cefebd443e56b88b
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43017 badge
[![CVE-2026-43017](https://cveledger.app/badge/CVE-2026-43017.svg)](https://cveledger.app/cve/CVE-2026-43017)

Record last updated .