high · 7.8

Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete

CVE-2025-40213 · published 24 Nov 2025

How serious is it

  • Severity: high, CVSS score 7.8 out of 10.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2025-40213?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • Linux Linux: 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a to < 31d6c9216aa1be18ba317239738f73b0b0c7b691, d71b98f253b079cbadc83266383f26fe7e9e103b to < 5c19daa93d9af29f1f46251b47e1ea66bcc8d679, 302a1f674c00dd5581ab8e493ef44767c5101aab to < 1c9aca1787e8395a2c59fef20e914467958969c5, 302a1f674c00dd5581ab8e493ef44767c5101aab to < e8785404de06a69d89dcdd1e9a0b6ea42dc6d327
  • Linux Linux: 6.17

How to check

  1. Find out whether you run the affected product and which version, then compare it with the versions above.

How to fix

Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
  1. Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
  2. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

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.

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON