CVE-2023-53998hwrng: virtio - Fix race on data_avail and actual data
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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
ID reserved
By Linux
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected f7f510ec195781c857ab76366a3e1c59e1caae42 – < 241ef15776a7c8505008db689175b320d345ecd3
- affected f7f510ec195781c857ab76366a3e1c59e1caae42 – < a43bcb0b661cbbf3ad797d2aee6b6fd06b8fc69d
- affected f7f510ec195781c857ab76366a3e1c59e1caae42 – < 77471e4912d3960dafe141e268c44be8024fe4dc
- affected f7f510ec195781c857ab76366a3e1c59e1caae42 – < c76d991b6f01a5d931e7053a73bc9524975a5215
- affected f7f510ec195781c857ab76366a3e1c59e1caae42 – < 22c30022cde6e2c88612b3a499223cfa912f1bc7
- affected f7f510ec195781c857ab76366a3e1c59e1caae42 – < 318657b4c2077289659f1cd9e2a34f6a3b208e3e
- affected f7f510ec195781c857ab76366a3e1c59e1caae42 – < 2fc91f156b3f3446a1bce80cf4adedcbf41271c2
- affected f7f510ec195781c857ab76366a3e1c59e1caae42 – < ac52578d6e8d300dd50f790f29a24169b1edd26c
- affected 2.6.26
- unaffected < 2.6.26
- unaffected 4.19.291 – ≤ 4.19.*
- unaffected 5.4.251 – ≤ 5.4.*
- unaffected 5.10.188 – ≤ 5.10.*
- unaffected 5.15.121 – ≤ 5.15.*
- unaffected 6.1.39 – ≤ 6.1.*
- unaffected 6.3.13 – ≤ 6.3.*
- unaffected 6.4.4 – ≤ 6.4.*
- unaffected 6.5 – ≤ *
References
References8
- https://git.kernel.org/stable/c/241ef15776a7c8505008db689175b320d345ecd3 (opens in a new tab)
- https://git.kernel.org/stable/c/a43bcb0b661cbbf3ad797d2aee6b6fd06b8fc69d (opens in a new tab)
- https://git.kernel.org/stable/c/77471e4912d3960dafe141e268c44be8024fe4dc (opens in a new tab)
- https://git.kernel.org/stable/c/c76d991b6f01a5d931e7053a73bc9524975a5215 (opens in a new tab)
- https://git.kernel.org/stable/c/22c30022cde6e2c88612b3a499223cfa912f1bc7 (opens in a new tab)
- https://git.kernel.org/stable/c/318657b4c2077289659f1cd9e2a34f6a3b208e3e (opens in a new tab)
- https://git.kernel.org/stable/c/2fc91f156b3f3446a1bce80cf4adedcbf41271c2 (opens in a new tab)
- https://git.kernel.org/stable/c/ac52578d6e8d300dd50f790f29a24169b1edd26c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-205151 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53998)Record last updated .