Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| tickbh | ProcessLock | unknown |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-28251 | process_lock has a Potential Unsound issue in unlock |
Github GHSA |
GHSA-6v24-6wgf-8vj6 | process_lock has a Potential Unsound issue in unlock |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.276% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tickbh
Tickbh process Lock |
|
| CPEs | cpe:2.3:a:tickbh:process_lock:0.1.0:*:*:*:*:rust:*:* | |
| Vendors & Products |
Tickbh
Tickbh process Lock |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The process_lock crate 0.1.0 for Rust allows data races in unlock. | |
| Weaknesses | CWE-362 | |
| References |
| |
| Metrics |
cvssV3_1
|
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')