> If this is of concern in your application, use getrandom(2) or /dev/random instead.
These bugs affect getrandom too.
> Multiple callers, including sys_getrandom(..., flags=0), attempt to wait for the
> RNG to become cryptographically safe before reading from it by checking for
> crng_ready() and waiting if necessary. However, crng_ready() only checks for
> `crng_init > 0`, and `crng_init==1` does not imply that the RNG is
> cryptographically safe.