# CVE-2025-48752: Process Sync has a Potential Unsound Issue in SharedMutex

> A missing mutex unlock check in the process-sync crate allows use-after-free, potentially leading to code execution or crashes.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 24 May 2025
- **Updated:** 24 May 2025
- **Also known as:** GHSA-mqwx-r894-9hfp

## What is CVE-2025-48752?

CVE-2025-48752 is a low-severity use after free vulnerability in Forestryks process-sync-rs, published on 24 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the process-sync crate 0.2.2 for Rust, the drop function lacks a check for whether the pthread_mutex is unlocked.

Weakness: CWE-416 (Use After Free)

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

2 open source packages ship an affected version, including process-sync. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `process-sync` | crates.io | All versions to 0.2.2 | None |
| `process-sync` | crates.io | All versions to 0.2.2 | None |

Products: Forestryks Process-Sync.

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

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

## Is CVE-2025-48752 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48752 is a low-severity use after free vulnerability in Forestryks process-sync-rs, published on 24 May 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-48752 in the wild and no public exploit code.

Affected packages and fixed versions:
- process-sync (crates.io): affected all versions up to 0.2.2; no fix listed
- process-sync (crates.io): affected all versions up to 0.2.2; no fix listed

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-48752/ (Markdown: https://insights.sbomify.com/CVE-2025-48752/index.md)
```

## Sources

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

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