CVE-2023-53998: 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 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).
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a race condition in the virtio random-number generator driver. On affected virtualized Linux systems, a reader may observe availability before the new random data is properly synchronized. The source does not provide CVSS, impact detail, or active exploitation evidence.
Executive priority
Handle through normal kernel patch management unless the environment heavily depends on virtualized Linux guests. Escalate if vendor guidance later assigns higher severity or identifies concrete security impact.
Technical view
The virtio hwrng driver could start a new entropy request when data_avail reached zero, leaving no synchronization between the completion writer and the next reader. Linux fixed this by using release/acquire semantics around data_avail and removing redundant zeroing.
Likely exposure
Exposure is most likely on Linux virtual machines or guests using the virtio-rng driver and running affected kernel versions or unpatched downstream builds. The source lists Linux versions from 2.6.26 through 6.5 as affected, with multiple stable fix commits.
Exploitation context
The provided sources do not claim exploitation in the wild, public exploit availability, or KEV listing. Treat this as a kernel correctness and synchronization vulnerability until vendor advisories provide more impact detail.
Researcher notes
Evidence is limited to the kernel fix description and CVE metadata. No CWE, CVSS vector, exploit status, or precise security consequence is provided. Analysis should avoid assuming entropy prediction or privilege impact without additional vendor evidence.
Mitigation direction
Update affected Linux kernels through your distribution or kernel vendor.
Confirm the relevant stable fix is included in deployed kernel builds.
Prioritize virtualized Linux guests using virtio-rng.
Check vendor guidance for any additional mitigations or operational caveats.
Validation and detection
Inventory Linux hosts and guests using virtio-rng.
Map deployed kernel versions to vendor fixed packages.
Review kernel changelogs for the referenced virtio hwrng fix commits.
Confirm no unsupported affected kernels remain in production.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-53998 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 10:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.