# Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete

CVE record · `CVE-2025-40213`

- **Identifiers:** `CVE-2025-40213`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Nov 2025
- **Updated:** 21 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Nov 2025, 15:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a to before 31d6c9216aa1be18ba317239738f73b0b0c7b691` (git)
  - affected: `d71b98f253b079cbadc83266383f26fe7e9e103b to before 5c19daa93d9af29f1f46251b47e1ea66bcc8d679` (git)
  - affected: `302a1f674c00dd5581ab8e493ef44767c5101aab to before 1c9aca1787e8395a2c59fef20e914467958969c5` (git)
  - affected: `302a1f674c00dd5581ab8e493ef44767c5101aab to before e8785404de06a69d89dcdd1e9a0b6ea42dc6d327` (git)
  - affected: `87a1f16f07c6c43771754075e08f45b41d237421` (git)
  - affected: `6.6.140 to before 6.6.160` (semver)
  - affected: `6.16.10 to before 6.17` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.17`
  - unaffected: `before 6.17` (semver)
  - unaffected: `6.6.160 to 6.6.*, inclusive` (semver)
  - unaffected: `6.17.8 to 6.17.*, inclusive` (semver)
  - unaffected: `6.18 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 9th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 24 Nov 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2025-40213](https://www.cve.org/CVERecord?id=CVE-2025-40213)
- [NVD: CVE-2025-40213](https://nvd.nist.gov/vuln/detail/CVE-2025-40213)

### References from the CNA

- <https://git.kernel.org/stable/c/31d6c9216aa1be18ba317239738f73b0b0c7b691>
- <https://git.kernel.org/stable/c/5c19daa93d9af29f1f46251b47e1ea66bcc8d679>
- <https://git.kernel.org/stable/c/1c9aca1787e8395a2c59fef20e914467958969c5>
- <https://git.kernel.org/stable/c/e8785404de06a69d89dcdd1e9a0b6ea42dc6d327>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-40213>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-40213/>. Everything for agents: <https://agentprime.io/llms.txt>.
