# CVE-2025-2329: High traffic causes corrupt SPI packets in OpenThread leading to denial of service

> High traffic causes corrupt SPI packets in Silicon Labs OpenThread RCP, leading to host resets and denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **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:** 25 Jul 2025
- **Updated:** 4 Aug 2025
- **Also known as:** GHSA-q46p-vh9h-4p2c

## What is CVE-2025-2329?

CVE-2025-2329 is a medium-severity denial of service vulnerability in silabs.com OpenThread, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In high traffic environments, a Silicon Labs OpenThread RCP (see impacted versions) fails to clear the SPI transmit buffer and may send a corrupt packet over SPI to its host,  causing the host to reset the RCP which results in a denial of service.

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2025-2329?


## How do I fix CVE-2025-2329?

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

## Is CVE-2025-2329 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2329 and fix it if it is affected.

What it is: CVE-2025-2329 is a medium-severity denial of service vulnerability in silabs.com OpenThread, published on 25 Jul 2025. 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-2025-2329 in the wild and no public exploit code.

Affected product: silabs.com OpenThread. 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-2025-2329/ (Markdown: https://insights.sbomify.com/CVE-2025-2329/index.md)
```

## Sources

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

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