<?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>Wed, 30 Sep 2026 01:00:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48629 — crypto: qcom-rng - ensure buffer for generate is completely filled</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-48629</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;crypto: qcom-rng - ensure buffer for generate is completely filled&lt;/p&gt;
&lt;p&gt;The generate function in struct rng_alg expects that the destination
buffer is completely filled if the function returns 0. qcom_rng_read()
can run into a situation where the buffer is partially filled with
randomness and the remaining part of the buffer is zeroed since
qcom_rng_generate() doesn&amp;#39;t check the return value. This issue can
be reproduced by running the following from libkcapi:&lt;/p&gt;
&lt;p&gt;kcapi-rng -b 9000000 &amp;gt; OUTFILE&lt;/p&gt;
&lt;p&gt;The generated OUTFILE will have three huge sections that contain all
zeros, and this is caused by the code where the test
&amp;#39;val &amp;amp; PRNG_STATUS_DATA_AVAIL&amp;#39; fails.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix this issue by ensuring that qcom_rng_read() always returns
with a full buffer if the function returns success. Let&amp;#39;s also have
qcom_rng_generate() return the correct value.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s some statistics from the ent project
(https://www.fourmilab.ch/random/) that shows information about the
quality of the generated numbers:&lt;/p&gt;
&lt;p&gt;$ ent -c qcom-random-before
    Value Char Occurrences Fraction
      0           606748   0.067416
      1            33104   0.003678
      2            33001   0.003667
    ...
    253   �        32883   0.003654
    254   �        33035   0.003671
    255   �        33239   0.003693&lt;/p&gt;
&lt;p&gt;Total:       9000000   1.000000&lt;/p&gt;
&lt;p&gt;Entropy = 7.811590 bits per byte.&lt;/p&gt;
&lt;p&gt;Optimum compression would reduce the size
    of this 9000000 byte f…&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;crypto: qcom-rng - ensure buffer for generate is completely filled&lt;/p&gt;
&lt;p&gt;The generate function in struct rng_alg expects that the destination
buffer is completely filled if the function returns 0. qcom_rng_read()
can run into a situation where the buffer is partially filled with
randomness and the remaining part of the buffer is zeroed since
qcom_rng_generate() doesn&amp;#39;t check the return value. This issue can
be reproduced by running the following from libkcapi:&lt;/p&gt;
&lt;p&gt;kcapi-rng -b 9000000 &amp;gt; OUTFILE&lt;/p&gt;
&lt;p&gt;The generated OUTFILE will have three huge sections that contain all
zeros, and this is caused by the code where the test
&amp;#39;val &amp;amp; PRNG_STATUS_DATA_AVAIL&amp;#39; fails.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix this issue by ensuring that qcom_rng_read() always returns
with a full buffer if the function returns success. Let&amp;#39;s also have
qcom_rng_generate() return the correct value.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s some statistics from the ent project
(https://www.fourmilab.ch/random/) that shows information about the
quality of the generated numbers:&lt;/p&gt;
&lt;p&gt;$ ent -c qcom-random-before
    Value Char Occurrences Fraction
      0           606748   0.067416
      1            33104   0.003678
      2            33001   0.003667
    ...
    253   �        32883   0.003654
    254   �        33035   0.003671
    255   �        33239   0.003693&lt;/p&gt;
&lt;p&gt;Total:       9000000   1.000000&lt;/p&gt;
&lt;p&gt;Entropy = 7.811590 bits per byte.&lt;/p&gt;
&lt;p&gt;Optimum compression would reduce the size
    of this 9000000 byte f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-48629</guid>
    </item>
  </channel>
</rss>
