# CVE-2024-7139: Denial of Service in Silicon Labs RS9116 Bluetooth SDK

> A buffer overflow in the Silicon Labs RS9116 Bluetooth SDK allows attackers to cause a temporary denial of service via crafted L2CAP packets.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2024
- **Updated:** 28 May 2025
- **Also known as:** GHSA-m2wv-vgv6-f4hv

## What is CVE-2024-7139?

CVE-2024-7139 is a medium-severity denial of service vulnerability in silabs.com RS9116 Bluetooth SDK, published on 19 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Due to an unchecked buffer length, a specially crafted L2CAP packet can cause a buffer overflow. This buffer overflow triggers an assert, which results in a temporary denial of service. 

If a watchdog timer is not enabled, a hard reset is required to recover the device.

Weakness: CWE-787 (Out-of-bounds Write), CWE-617 (Reachable Assertion)

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


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

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

## Is CVE-2024-7139 being exploited?

There is no known exploitation of CVE-2024-7139 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-7139 is a medium-severity denial of service vulnerability in silabs.com RS9116 Bluetooth SDK, published on 19 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7139 in the wild and no public exploit code.

Affected product: silabs.com RS9116 Bluetooth SDK. 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-7139/ (Markdown: https://insights.sbomify.com/CVE-2024-7139/index.md)
```

## Sources

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

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