An issue was discovered in the linked-hash-map crate before 0.5.3 for Rust. It creates an uninitialized NonNull pointer, which violates a non-null constraint.
{
"binaries": [
{
"binary_name": "librust-linked-hash-map+heapsize-dev",
"binary_version": "0.5.2-2"
},
{
"binary_name": "librust-linked-hash-map+heapsize-impl-dev",
"binary_version": "0.5.2-2"
},
{
"binary_name": "librust-linked-hash-map+serde-dev",
"binary_version": "0.5.2-2"
},
{
"binary_name": "librust-linked-hash-map+serde-impl-dev",
"binary_version": "0.5.2-2"
},
{
"binary_name": "librust-linked-hash-map+serde-test-dev",
"binary_version": "0.5.2-2"
},
{
"binary_name": "librust-linked-hash-map-dev",
"binary_version": "0.5.2-2"
}
]
}
{
"binaries": [
{
"binary_name": "librust-linked-hash-map+heapsize-dev",
"binary_version": "0.5.4-1"
},
{
"binary_name": "librust-linked-hash-map+serde-dev",
"binary_version": "0.5.4-1"
},
{
"binary_name": "librust-linked-hash-map+serde-impl-dev",
"binary_version": "0.5.4-1"
},
{
"binary_name": "librust-linked-hash-map+serde-test-dev",
"binary_version": "0.5.4-1"
},
{
"binary_name": "librust-linked-hash-map-dev",
"binary_version": "0.5.4-1"
}
]
}