CVE-2023-53998
published 2025-12-24CVE-2023-53998: 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…
PriorityP422low3.3
EPSS
0.18%
8.2th percentile
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).
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.52-1 (bookworm) | linux 6.1.52-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= f7f510ec195781c857ab76366a3e1c59e1caae42 < 241ef15776a7c8505008db689175b320d345ecd3 | 241ef15776a7c8505008db689175b320d345ecd3 |
| linux | linux | >= f7f510ec195781c857ab76366a3e1c59e1caae42 < a43bcb0b661cbbf3ad797d2aee6b6fd06b8fc69d | a43bcb0b661cbbf3ad797d2aee6b6fd06b8fc69d |
| linux | linux | >= f7f510ec195781c857ab76366a3e1c59e1caae42 < 77471e4912d3960dafe141e268c44be8024fe4dc | 77471e4912d3960dafe141e268c44be8024fe4dc |
| linux | linux | >= f7f510ec195781c857ab76366a3e1c59e1caae42 < c76d991b6f01a5d931e7053a73bc9524975a5215 | c76d991b6f01a5d931e7053a73bc9524975a5215 |
| linux | linux | >= f7f510ec195781c857ab76366a3e1c59e1caae42 < 22c30022cde6e2c88612b3a499223cfa912f1bc7 | 22c30022cde6e2c88612b3a499223cfa912f1bc7 |
| linux | linux | >= f7f510ec195781c857ab76366a3e1c59e1caae42 < 318657b4c2077289659f1cd9e2a34f6a3b208e3e | 318657b4c2077289659f1cd9e2a34f6a3b208e3e |
| linux | linux | >= f7f510ec195781c857ab76366a3e1c59e1caae42 < 2fc91f156b3f3446a1bce80cf4adedcbf41271c2 | 2fc91f156b3f3446a1bce80cf4adedcbf41271c2 |
| linux | linux | >= f7f510ec195781c857ab76366a3e1c59e1caae42 < ac52578d6e8d300dd50f790f29a24169b1edd26c | ac52578d6e8d300dd50f790f29a24169b1edd26c |
| linux | linux_kernel | >= 0 < 5.10.191-1 | 5.10.191-1 |
| linux | linux_kernel | >= 0 < 6.1.52-1 | 6.1.52-1 |
| linux | linux_kernel | >= 0 < 6.4.4-1 | 6.4.4-1 |
| linux | linux_kernel | >= 0 < 6.4.4-1 | 6.4.4-1 |
| linux | linux_kernel | >= 2.6.26 < 4.19.291 | 4.19.291 |
| linux | linux_kernel | >= 4.20.0 < 5.4.251 | 5.4.251 |
| linux | linux_kernel | >= 5.11.0 < 5.15.121 | 5.15.121 |
| linux | linux_kernel | >= 5.16.0 < 6.1.39 | 6.1.39 |
| linux | linux_kernel | >= 5.5.0 < 5.10.188 | 5.10.188 |
| linux | linux_kernel | >= 6.2.0 < 6.3.13 | 6.3.13 |
| linux | linux_kernel | >= 6.4.0 < 6.4.4 | 6.4.4 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: hwrng: virtio - Fix race on data_avail and actual data
vendor_redhat·2025-12-24·CVSS 3.3
CVE-2023-53998 [LOW] CWE-820 kernel: hwrng: virtio - Fix race on data_avail and actual data
kernel: hwrng: virtio - Fix race on data_avail and actual data
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 th
Debian
CVE-2023-53998: linux - In the Linux kernel, the following vulnerability has been resolved: hwrng: virt...
vendor_debian·2023
CVE-2023-53998 CVE-2023-53998: linux - In the Linux kernel, the following vulnerability has been resolved: hwrng: virt...
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 dat
OSV
CVE-2023-53998: 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
osv·2025-12-24
CVE-2023-53998 CVE-2023-53998: 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
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 dat
GHSA
GHSA-g2vv-m9x5-457j: In the Linux kernel, the following vulnerability has been resolved:
hwrng: virtio - Fix race on data_avail and actual data
The virtio rng device kic
ghsa_unreviewed·2025-12-24
CVE-2023-53998 GHSA-g2vv-m9x5-457j: In the Linux kernel, the following vulnerability has been resolved:
hwrng: virtio - Fix race on data_avail and actual data
The virtio rng device kic
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 o
OSV
hwrng: virtio - Fix race on data_avail and actual data
osv·2025-12-24
CVE-2023-53998 hwrng: virtio - Fix race on data_avail and actual data
hwrng: virtio - Fix race on data_avail and actual data
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 co
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2023-53998 kernel: hwrng: virtio - Fix race on data_avail and actual data
bugzilla·2025-12-24
CVE-2023-53998 [LOW] CVE-2023-53998 kernel: hwrng: virtio - Fix race on data_avail and actual data
CVE-2023-53998 kernel: hwrng: virtio - Fix race on data_avail and actual data
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 loa
Wiz
CVE-2023-53998 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2023-53998 CVE-2023-53998 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2023-53998 :
Linux Kernel vulnerability analysis and mitigation
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
acqu
https://git.kernel.org/stable/c/22c30022cde6e2c88612b3a499223cfa912f1bc7https://git.kernel.org/stable/c/241ef15776a7c8505008db689175b320d345ecd3https://git.kernel.org/stable/c/2fc91f156b3f3446a1bce80cf4adedcbf41271c2https://git.kernel.org/stable/c/318657b4c2077289659f1cd9e2a34f6a3b208e3ehttps://git.kernel.org/stable/c/77471e4912d3960dafe141e268c44be8024fe4dchttps://git.kernel.org/stable/c/a43bcb0b661cbbf3ad797d2aee6b6fd06b8fc69dhttps://git.kernel.org/stable/c/ac52578d6e8d300dd50f790f29a24169b1edd26chttps://git.kernel.org/stable/c/c76d991b6f01a5d931e7053a73bc9524975a5215
2025-12-24
Published