Description
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | rust-lock-api | 0.4.5-1 | — |
| Debian 13 | rust-lock-api | 0.4.5-1 | — |
| Debian 12 | rust-lock-api | 0.4.5-1 | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | rust-lock-api | No fix yet | — |
| Ubuntu 26.04 LTS | rust-lock-api | No fix yet | — |
| Ubuntu 25.10 | rust-lock-api | No fix yet | — |
| Ubuntu 24.04 LTS | rust-lock-api | No fix yet | — |
| Ubuntu 22.04 LTS | rust-lock-api | No fix yet | — |
Show 1 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 20.04 LTS | rust-lock-api | No fix yet | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| crates.io | lock_api | < 0.4.2 | 0.4.2 | GHSA-5wg8-7c9q-794v |
| crates.io | lock_api | >= 0.0.0-0, < 0.4.2 | 0.4.2 | RUSTSEC-2020-0070 |