hwrng: virtio - Fix race on data_avail and actual data
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: hwrng: virtio - Fix race on data_avail and actual data The virtio rng device kicks off a new entropy request whenever the data available reaches zero. When a new request occurs at the end of a read operation, that is, when the result of that request is only needed by the next reader, then there is a race between the writing of the new data and the next reader. This is because there is no synchronisation whatsoever between the writer and the reader. Fix this by writing data_avail with smp_store_release and reading it with smp_load_acquire when we first enter read. The subsequent reads are safe because they're either protected by the first load acquire, or by the completion mechanism. Also remove the redundant zeroing of data_idx in random_recv_done (data_idx must already be zero at this point) and data_avail in request_entropy (ditto).
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.26
References 8
git.kernel.org
- stable/c/241ef15776a7c8505008db689175b320d345ecd3
- stable/c/a43bcb0b661cbbf3ad797d2aee6b6fd06b8fc69d
- stable/c/77471e4912d3960dafe141e268c44be8024fe4dc
- stable/c/c76d991b6f01a5d931e7053a73bc9524975a5215
- stable/c/22c30022cde6e2c88612b3a499223cfa912f1bc7
- stable/c/318657b4c2077289659f1cd9e2a34f6a3b208e3e
- stable/c/2fc91f156b3f3446a1bce80cf4adedcbf41271c2
- stable/c/ac52578d6e8d300dd50f790f29a24169b1edd26c