https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 15:15:41 +0000 https://cve.radiocsirt.org/vuln/cve-2020-35905 <p>An issue was discovered in the futures-util crate before 0.3.7 for Rust. MutexGuard::map can cause a data race for certain closure situations (in safe code).</p> <p>An issue was discovered in the futures-util crate before 0.3.7 for Rust. MutexGuard::map can cause a data race for certain closure situations (in safe code).</p> https://cve.radiocsirt.org/vuln/cve-2020-35905 https://cve.radiocsirt.org/vuln/ghsa-rh4w-94hh-9943 <p><strong>Affected:</strong> crates.io: futures-util</p> <p>Affected versions of the crate had a Send/Sync implementation for MappedMutexGuard that only considered variance on T, while MappedMutexGuard dereferenced to U.</p> <p>This could of led to data races in safe Rust code when a closure used in MutexGuard::map() returns U that is unrelated to T.</p> <p>The issue was fixed by fixing Send and Sync implementations, and by adding a PhantomData&lt;&amp;&#39;a mut U&gt; marker to the MappedMutexGuard type to tell the compiler that the guard is over U too.</p> <p><strong>Affected:</strong> crates.io: futures-util</p> <p>Affected versions of the crate had a Send/Sync implementation for MappedMutexGuard that only considered variance on T, while MappedMutexGuard dereferenced to U.</p> <p>This could of led to data races in safe Rust code when a closure used in MutexGuard::map() returns U that is unrelated to T.</p> <p>The issue was fixed by fixing Send and Sync implementations, and by adding a PhantomData&lt;&amp;&#39;a mut U&gt; marker to the MappedMutexGuard type to tell the compiler that the guard is over U too.</p> https://cve.radiocsirt.org/vuln/ghsa-rh4w-94hh-9943