CVE-2020-35912:
Data races in lock_api
4.7
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.12845%
CWE
Published
8/25/2021
Updated
6/13/2023
KEV Status
No
Technology
Rust
Technical Details
CVSS Vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
lock_api | rust | < 0.4.2 | 0.4.2 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from improper trait implementations (Send/Sync) on various guard types. The advisory explicitly lists MappedMutexGuard, MappedRwLockReadGuard, MappedRwLockWriteGuard, RwLockReadGuard, and RwLockWriteGuard as having unsound implementations. These guards' Deref and DerefMut implementations would allow accessing protected data across thread boundaries without proper synchronization. The pull request #262 in parking_lot (which uses lock_api) shows fixes to trait bounds verification, confirming that the core issue was in these guard types' synchronization primitive implementations.