CVE-2023-53998

hwrng: virtio - Fix race on data_avail and actual data

N/A
Published: December 24, 2025 at 10:55 AM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.26 ≤ v < 4.19.2912.6.26 ≤ v < 5.10.1882.6.26 ≤ v < 5.15.1212.6.26 ≤ v < 5.4.2512.6.26 ≤ v < 6.1.392.6.26 ≤ v < 6.3.132.6.26 ≤ v < 6.4.42.6.26 ≤ v < 6.52.6.26f7f510ec195781c857ab76366a3e1c59e1caae42
Vendor states this is fixed in 22c30022cde6e2c88612b3a499223cfa912f1bc7 (fixed)
Vendor states this is fixed in 241ef15776a7c8505008db689175b320d345ecd3 (fixed)
Vendor states this is fixed in 2fc91f156b3f3446a1bce80cf4adedcbf41271c2 (fixed)
Vendor states this is fixed in 318657b4c2077289659f1cd9e2a34f6a3b208e3e (fixed)
Vendor states this is fixed in 77471e4912d3960dafe141e268c44be8024fe4dc (fixed)
Vendor states this is fixed in a43bcb0b661cbbf3ad797d2aee6b6fd06b8fc69d (fixed)
Vendor states this is fixed in ac52578d6e8d300dd50f790f29a24169b1edd26c (fixed)
Vendor states this is fixed in c76d991b6f01a5d931e7053a73bc9524975a5215 (fixed)
Vendor states this is fixed in 2.6.26 (unaffected)
Vendor states this is fixed in 4.19.291 (unaffected)
Vendor states this is fixed in 5.10.188 (unaffected)
Vendor states this is fixed in 5.15.121 (unaffected)
Vendor states this is fixed in 5.4.251 (unaffected)
Vendor states this is fixed in 6.1.39 (unaffected)
Vendor states this is fixed in 6.3.13 (unaffected)
Vendor states this is fixed in 6.4.4 (unaffected)
Vendor states this is fixed in 6.5 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card