rustsec/advisory-db
1
0
Fork 0
mirror of https://github.com/rustsec/advisory-db.git synced 2026-07-16 00:12:29 -04:00
Code Issues Packages Projects Releases Wiki Activity

Remove duplicative info in RUSTSEC-2026-0097

Browse Source
This commit is contained in:
xtqqczze
2026-04-17 16:39:46 +01:00
committed by Dirkjan Ochtman
parent 350e2f43cc
commit f9b2158acd
1 changed files with 0 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
crates/rand/RUSTSEC-2026-0097.md
View File

@@ -30,5 +30,3 @@ It has been reported (by @lopopolo) that the `rand` library is [unsound](https:/
- Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
`TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
Affected versions of `rand` are `>= 0.7, < 0.8.6`, >= `0.9.0, < 0.9.3`, and `0.10.0`.