Lucene search
+L

11 matches found

RedhatCVE
RedhatCVE
•added 2026/01/07 9:31 a.m.•9 views

CVE-2019-16137

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...

7.8CVSS7.2AI score0.01423EPSS
SaveExploits0References1
EUVD
EUVD
•added 2025/10/07 12:30 a.m.•17 views

EUVD-2021-1759

Malware in sbrugna...

7.8CVSS7.4AI score0.01423EPSS
SaveExploits0References7
SUSE CVE
SUSE CVE
•added 2023/02/15 4:08 a.m.•11 views

SUSE CVE-2019-16137

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...

7.8CVSS7.4AI score0.01423EPSS
SaveExploits0References3
RustSec
RustSec
•added 2019/11/21 12:00 p.m.•24 views

spin is no longer actively maintained

The author of the spin crate does not have time or interest to maintain it. Consider the following alternatives all of which support nostd: - conquer-once - lockapi a subproject of parkinglot - spinningtop spinlock crate built on lockapi - spinning...

2.3AI score
SaveExploits0Affected Software1
OSV
OSV
•added 2019/11/21 12:00 p.m.•19 views

RUSTSEC-2019-0031 spin is no longer actively maintained

The author of the spin crate does not have time or interest to maintain it. Consider the following alternatives all of which support nostd: - conquer-once - lockapi a subproject of parkinglot - spinningtop spinlock crate built on lockapi - spinning...

7.1AI score
SaveExploits0References3
OSV
OSV
•added 2019/09/09 12:15 p.m.•13 views

CVE-2019-16137

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...

7.5CVSS7.5AI score
SaveExploits0References1
NVD
NVD
•added 2019/09/09 12:15 p.m.•27 views

CVE-2019-16137

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...

7.8CVSS7.5AI score0.01423EPSS
SaveExploits0References1
OSV
OSV
•added 2019/09/09 12:15 p.m.•94 views

DEBIAN-CVE-2019-16137

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...

7.5CVSS7.3AI score0.01423EPSS
SaveExploits0References1
UbuntuCve
UbuntuCve
•added 2019/09/09 12:15 p.m.•24 views

CVE-2019-16137

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...

7.8CVSS7.1AI score0.01423EPSS
SaveExploits0References3
Prion
Prion
•added 2019/09/09 12:15 p.m.•27 views

Privilege escalation

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...

7.8CVSS7.5AI score0.01423EPSS
SaveExploits0References1Affected Software1
CVE
CVE
•added 2019/09/09 11:45 a.m.•68 views

CVE-2019-16137

CVE-2019-16137 affects the spin crate for Rust (before version 0.5.2) where the RwLock memory ordering is mishandled. The underlying issue can allow two writers to acquire the lock simultaneously, violating mutual exclusion. This is documented across multiple sources (NVD, Red Hat, SUSE, OSV, Git...

7.8CVSS7.4AI score0.01423EPSS
SaveExploits0References1Affected Software1
Rows per page
Query Builder