Skip to content
Fencer Vulns
high 7.5

CVE-2019-16137 json

Wrong memory orderings violates mutual exclusion in spin

published 2019-08-27 7 y ago modified 2026-06-17 4 mo ago also GHSA-hv7x-f3pv-gpwr , RUSTSEC-2019-0013 , EUVD-2021-1759

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

An issue was discovered in the spin crate before 0.5.2 for Rust, when RwLock is used. Because memory ordering is mishandled, two writers can acquire the lock at the same time, violating mutual exclusion.

Patch / fix

  • crates.io spin 0.5.2
  • spin-rs_project spin-rs 0.5.2
  • rust-spin Debian 14, Debian 13, Debian 12 0.5.2-1

debian advisories DEBIAN-CVE-2019-16137

Exploit prediction

1.42% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 7.8 AV:N/AC:L/Au:N/C:N/I:N/A:C
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
crates.io spin
<0.5.2
>=0.0.0-0, <0.5.2
0.5.2

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.