Lucene search
+L

125 matches found

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.•67 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
Debian CVE
Debian CVE
•added 2019/09/09 11:45 a.m.•77 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
SaveExploits0
Cvelist
Cvelist
•added 2019/09/09 11:45 a.m.•37 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.5AI score0.01423EPSS
SaveExploits0References1
Rows per page
Query Builder