CVE-2025-48751: Race Condition
Published May 24, 2025
·Updated
The processlock crate 0.1.0 for Rust allows data races in unlock.
Affected Software
3 affected components
Rust process_lock crate
rust/process_lock<=0.1.0
Tickbh Process Lock Rust=0.1.0
Event History
May 24, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 AM
Affected Software
Advisory Published
via GitHub·03:30 AM
Frequently Asked Questions
1
What is the severity of CVE-2025-48751?
CVE-2025-48751 is classified as a medium severity vulnerability due to potential data races in the process_lock crate.
2
How do I fix CVE-2025-48751?
To fix CVE-2025-48751, update to a patched version of the process_lock crate or refactor the code to avoid using this vulnerable crate.
3
What is the impact of CVE-2025-48751?
CVE-2025-48751 allows data races during unlock operations, which can lead to undefined behavior in multithreaded applications.
4
Which versions of the process_lock crate are affected by CVE-2025-48751?
CVE-2025-48751 affects version 0.1.0 of the process_lock crate for Rust.
5
Is CVE-2025-48751 related to Rust programming security?
Yes, CVE-2025-48751 highlights a vulnerability in the Rust programming ecosystem that can compromise application security.