SECUFOCUSNOW
Home›CVE index›CVE-2025-40213
Review reviewHigh

CVE-2025-40213

Linux

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.

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2025.11.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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 product and versions

Product
Linux
Affected versions
>= d71b98f253b079cbadc83266383f26fe7e9e103b < 5c19daa93d9af29f1f46251b47e1ea66bcc8d679, >= 302a1f674c00dd5581ab8e493ef44767c5101aab < 1c9aca1787e8395a2c59fef20e914467958969c5, >= 302a1f674c00dd5581ab8e493ef44767c5101aab < e8785404de06a69d89dcdd1e9a0b6ea42dc6d327, >= 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a, >= 87a1f16f07c6c43771754075e08f45b41d237421, >= 6.6.140 < 6.7, >= 6.16.10 < 6.17, >= 6.17
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available