<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 11:53:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53998 — hwrng: virtio - Fix race on data_avail and actual data</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53998</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hwrng: virtio - Fix race on data_avail and actual data&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This is because there is no synchronisation whatsoever between the
writer and the reader.&lt;/p&gt;
&lt;p&gt;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&amp;#39;re either protected by the first load
acquire, or by the completion mechanism.&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hwrng: virtio - Fix race on data_avail and actual data&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This is because there is no synchronisation whatsoever between the
writer and the reader.&lt;/p&gt;
&lt;p&gt;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&amp;#39;re either protected by the first load
acquire, or by the completion mechanism.&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53998</guid>
    </item>
  </channel>
</rss>
