crypto: jitterentropy - replace long-held spinlock with mutex
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bb5530e4082446aac3a3d69780cd4dbfa4520013 · < 01d798e9feb30212952d4e992801ba6bd6a82351| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: jitterentropy - replace long-held spinlock with mutex
jent_kcapi_random() serializes the shared jitterentropy state, but it currently holds a spinlock across the jent_read_entropy() call. That path performs expensive jitter collection and SHA3 conditioning, so parallel readers can trigger stalls as contending waiters spin for the same lock.
To prevent non-preemptible lock hold, replace rng->jent_lock with a mutex so contended readers sleep instead of spinning on a shared lock held across expensive entropy generation.
From the CVE record · Linux
The Linux kernel jitterentropy RNG holds a spinlock during expensive entropy generation. Parallel readers can cause stalls as they contend for that lock. The input does not specify access requirements or user interaction.
Engineers running Linux kernels with the affected jitterentropy code should check their versions against the vendor advisory; affected versions are not specified.