CVE-2025-40213

published 24 Nov 2025 · updated 17 Nov 2026

Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5c19daa93d9af29f1f46251b47e1ea66bcc8d679, Kernel e8785404de06a69d89dcdd1e9a0b6ea42dc6d327, Kernel 6.17 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete There is a BUG: KASAN: stack-out-of-bounds in set_mesh_sync due to memcpy from badly declared on-stack flexible array. Another crash is in set_mesh_complete() due to double list_del via mgmt_pending_valid + mgmt_pending_remove. Use DEFINE_FLEX to declare the flexible array right, and don't memcpy outside bounds. As mgmt_pending_valid removes the cmd from list, use mgmt_pending_free, and also report status on error.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=d71b98f253b079cbadc83266383f26fe7e9e103b <5c19daa93d9af29f1f46251b47e1ea66bcc8d679, >=302a1f674c00dd5581ab8e493ef44767c5101aab <e8785404de06a69d89dcdd1e9a0b6ea42dc6d327, >=6.16.10 <6.17, >=6.6.140 <6.6.160, =6.17, =87a1f16f07c6c43771754075e08f45b41d237421, >=0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a <31d6c9216aa1be18ba317239738f73b0b0c7b691, >=302a1f674c00dd5581ab8e493ef44767c5101aab <1c9aca1787e8395a2c59fef20e914467958969c55c19daa93d9af29f1f46251b47e1ea66bcc8d679, e8785404de06a69d89dcdd1e9a0b6ea42dc6d327, 6.17, 6.6.160, 31d6c9216aa1be18ba317239738f73b0b0c7b691, 1c9aca1787e8395a2c59fef20e914467958969c5
linux-kernel: Kernel>=6.17.0 <6.17.8, >=6.6.140 <6.6.160, >=6.16.10 <6.176.17.8, 6.6.160, 6.17

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-40213 severity on Zeptric[![CVE-2025-40213](https://zeptric.io/badge/cve/CVE-2025-40213.svg)](https://zeptric.io/cve/CVE-2025-40213)