An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness.
{ "binaries": [ { "binary_version": "0.3.3-1", "binary_name": "librust-lock-api+owning-ref-dev" }, { "binary_version": "0.3.3-1", "binary_name": "librust-lock-api+serde-dev" }, { "binary_version": "0.3.3-1", "binary_name": "librust-lock-api-dev" } ] }
{ "binaries": [ { "binary_version": "0.4.5-1", "binary_name": "librust-lock-api+owning-ref-dev" }, { "binary_version": "0.4.5-1", "binary_name": "librust-lock-api+serde-dev" }, { "binary_version": "0.4.5-1", "binary_name": "librust-lock-api-dev" } ] }
{ "binaries": [ { "binary_version": "0.4.11-1", "binary_name": "librust-lock-api-dev" } ] }
{ "binaries": [ { "binary_version": "0.4.12-1", "binary_name": "librust-lock-api-dev" } ] }