# CVE-2024-40568: Memory corruption in n/a

> A buffer overflow in the Bluetooth mesh library allows remote attackers to execute arbitrary code via the pb_adv_handle_transaction_cont function.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2024
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-3jrq-ghjr-jwf2

## What is CVE-2024-40568?

CVE-2024-40568 is a critical memory corruption vulnerability in n/a, published on 18 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer Overflow vulnerability in btstack mesh commit before v.864e2f2b6b7878c8fab3cf5ee84ae566e3380c58 allows a remote attacker to execute arbitrary code via the pb_adv_handle_tranaction_cont function in the src/mesh/pb_adv.c component

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-40568?


## How do I fix CVE-2024-40568?

No fix has been published for CVE-2024-40568 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-40568 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40568 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-40568 and fix it if it is affected.

What it is: CVE-2024-40568 is a critical memory corruption vulnerability in n/a, published on 18 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40568 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-40568/ (Markdown: https://insights.sbomify.com/CVE-2024-40568/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-40568
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-40568
- OSV: https://osv.dev/vulnerability/CVE-2024-40568

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-40568/
Summaries are generated and may contain mistakes; the official description above is the record.