LiveActive security incident?Get immediate response
CVE Record

CVE-2025-40213: Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2025-40213 is a Linux kernel Bluetooth management flaw that can crash affected systems when mesh-related management handling reaches faulty code. The public record describes stack out-of-bounds memory access and double list deletion. No CVSS score, confirmed active exploitation, or product-specific advisory is provided in the bundle.

Executive priority

Track this as a patch-management item with uncertain severity. Prioritize internet-adjacent or physically exposed Linux assets using Bluetooth, but avoid emergency escalation unless vendor guidance or new exploitation evidence raises urgency.

Technical view

The kernel fix addresses set_mesh_sync copying from an incorrectly declared on-stack flexible array and set_mesh_complete calling list deletion twice through mgmt_pending_valid and mgmt_pending_remove. The patch uses DEFINE_FLEX, avoids out-of-bounds memcpy, frees pending commands correctly, and reports status on error.

Likely exposure

Exposure appears limited to Linux kernels containing the vulnerable Bluetooth MGMT mesh code. The bundle lists Linux kernel version metadata and stable commits, but does not identify distributions, devices, configurations, or remote reachability requirements.

Exploitation context

The bundle reports crashes detected as KASAN stack-out-of-bounds and double list deletion. It does not report public exploitation, KEV listing, exploit availability, required privileges, or attack vector. Treat exploitation status as unconfirmed.

Researcher notes

The CVE record is terse and kernel-specific. Key evidence is the resolved crash description and three stable commit references. Missing details include CVSS, CWE, trigger conditions, attacker position, and affected distribution mappings.

Mitigation direction

  • Check Linux vendor advisories for fixed kernel packages or backports.
  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Prioritize systems where Bluetooth and mesh management functionality are enabled.
  • If immediate patching is unavailable, review vendor guidance for Bluetooth risk reduction.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, appliances, and embedded devices.
  • Compare installed kernels against vendor advisories and the referenced stable commits.
  • Confirm whether Bluetooth support and mesh management paths are enabled.
  • Review kernel logs for related Bluetooth MGMT crashes or KASAN reports.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-40213 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd71b98f253b079cbadc83266383f26fe7e9e103b, 302a1f674c00dd5581ab8e493ef44767c5101aab, 302a1f674c00dd5581ab8e493ef44767c5101aab, 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a, 87a1f16f07c6c43771754075e08f45b41d237421, 6.6.140, 6.16.10unaffected
LinuxLinux6.17, 0, 6.17.8, 6.18affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.