CVE-2026-43017
What it 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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 6.1.168
- Linux Kernel < 6.6.134
- Linux Kernel < 6.12.81
- Linux Kernel < 6.18.22
- Linux Kernel < 6.19.12
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43017.md and follow it. Check whether this project is affected by CVE-2026-43017. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- 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
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