# CVE-2025-51006: Use after free in n/a

> A local attacker can cause a denial of service via memory corruption by providing a crafted pcap file to tcprewrite.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Sep 2025
- **Updated:** 22 Sep 2025
- **Also known as:** DEBIAN-CVE-2025-51006, GHSA-7rv6-hjpp-g74c, UBUNTU-CVE-2025-51006

## What is CVE-2025-51006?

CVE-2025-51006 is a high-severity use after free vulnerability in Broadcom Tcpreplay, published on 22 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Within tcpreplay's tcprewrite, a double free vulnerability has been identified in the dlt_linuxsll2_cleanup() function in plugins/dlt_linuxsll2/linuxsll2.c. This vulnerability is triggered when tcpedit_dlt_cleanup() indirectly invokes the cleanup routine multiple times on the same memory region. By supplying a specifically crafted pcap file to the tcprewrite binary, a local attacker can exploit this flaw to cause a Denial of Service (DoS) via memory corruption.

Weakness: CWE-415 (Double Free)

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

It affects 1 product.


Products: Broadcom Tcpreplay.

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

No fix published yet.

## Is CVE-2025-51006 being exploited?

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

## Other vulnerabilities in Broadcom Tcpreplay

- [CVE-2018-18408](https://insights.sbomify.com/CVE-2018-18408/): Use after free in n/a (critical 9.8)
- [CVE-2020-12740](https://insights.sbomify.com/CVE-2020-12740/): Memory corruption in n/a (critical 9.1)
- [CVE-2022-37047](https://insights.sbomify.com/CVE-2022-37047/): Memory corruption in n/a (high 7.8)
- [CVE-2022-37048](https://insights.sbomify.com/CVE-2022-37048/): Memory corruption in n/a (high 7.8)
- [CVE-2022-37049](https://insights.sbomify.com/CVE-2022-37049/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-51006 is a high-severity use after free vulnerability in Broadcom Tcpreplay, published on 22 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51006 exists.

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

## Sources

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

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