diff options
| author | Theodore Ts'o <[email protected]> | 2018-04-11 15:23:56 -0400 |
|---|---|---|
| committer | Theodore Ts'o <[email protected]> | 2018-04-14 11:59:19 -0400 |
| commit | 8ef35c866f8862df074a49a93b0309725812dea8 (patch) | |
| tree | 982e05c942d90c435fdb4dc0f303ae2c4cac22d6 /lib/memory-notifier-error-inject.c | |
| parent | dc12baacb95f205948f64dc936a47d89ee110117 (diff) | |
random: set up the NUMA crng instances after the CRNG is fully initialized
Until the primary_crng is fully initialized, don't initialize the NUMA
crng nodes. Otherwise users of /dev/urandom on NUMA systems before
the CRNG is fully initialized can get very bad quality randomness. Of
course everyone should move to getrandom(2) where this won't be an
issue, but there's a lot of legacy code out there. This related to
CVE-2018-1108.
Reported-by: Jann Horn <[email protected]>
Fixes: 1e7f583af67b ("random: make /dev/urandom scalable for silly...")
Cc: [email protected] # 4.8+
Signed-off-by: Theodore Ts'o <[email protected]>
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions