Strix
26.1K

CVE-2023-53998

UnknownEPSS 0.18%

Last modified

CVE-2023-53998 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

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

Metrics

EPSS Probability
0.18%

7.5th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= f7f510ec195781c857ab76366a3e1c59e1caae42, < 241ef15776a7c8505008db689175b320d345ecd3; >= f7f510ec195781c857ab76366a3e1c59e1caae42, < a43bcb0b661cbbf3ad797d2aee6b6fd06b8fc69d; >= f7f510ec195781c857ab76366a3e1c59e1caae42, < 77471e4912d3960dafe141e268c44be8024fe4dc; >= f7f510ec195781c857ab76366a3e1c59e1caae42, < c76d991b6f01a5d931e7053a73bc9524975a5215; >= f7f510ec195781c857ab76366a3e1c59e1caae42, < 22c30022cde6e2c88612b3a499223cfa912f1bc7; >= f7f510ec195781c857ab76366a3e1c59e1caae42, < 318657b4c2077289659f1cd9e2a34f6a3b208e3e; >= f7f510ec195781c857ab76366a3e1c59e1caae42, < 2fc91f156b3f3446a1bce80cf4adedcbf41271c2; >= f7f510ec195781c857ab76366a3e1c59e1caae42, < ac52578d6e8d300dd50f790f29a24169b1edd26c
LinuxLinux2.6.26

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is 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 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).
How severe is CVE-2023-53998?
Severity scoring for CVE-2023-53998 is pending analysis. The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2023-53998?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2023

View all 2023CVEs →

Are you affected by CVE-2023-53998?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST