From 6a769d1d24139733a98fc7decc91dd682a1f314d Mon Sep 17 00:00:00 2001
From: Ben Kimock <kimockb@gmail.com>
Date: Tue, 7 Jun 2022 19:10:09 -0400
Subject: [PATCH] Report data race/memory corruption in crossbeam 0.2 (#1260)

---
 crates/crossbeam/RUSTSEC-0000-0000.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 crates/crossbeam/RUSTSEC-0000-0000.md

diff --git a/crates/crossbeam/RUSTSEC-0000-0000.md b/crates/crossbeam/RUSTSEC-0000-0000.md
new file mode 100644
index 0000000..b004c8d
--- /dev/null
+++ b/crates/crossbeam/RUSTSEC-0000-0000.md
@@ -0,0 +1,16 @@
+```toml
+[advisory]
+id = "RUSTSEC-0000-0000"
+package = "crossbeam"
+date = "2022-06-07"
+categories = ["thread-safety", "memory-corruption"]
+url = "https://github.com/crossbeam-rs/crossbeam/pull/98"
+
+[versions]
+patched = [">= 0.3.0"]
+```
+
+# `MsQueue` `push`/`pop` use the wrong orderings
+
+Affected versions of this crate use orderings which are too weak to support this data structure.
+It is likely this has caused memory corruption in the wild: <https://github.com/crossbeam-rs/crossbeam/issues/97#issuecomment-412785919>.