An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.
{ "binaries": [ { "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", "binary_version": "0.3.3-1" } ] }
{ "binaries": [ { "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", "binary_version": "0.4.5-1" } ] }
{ "binaries": [ { "binary_name": "librust-lock-api-dev", "binary_version": "0.4.11-1" } ] }
{ "binaries": [ { "binary_name": "librust-lock-api-dev", "binary_version": "0.4.12-1" } ] }