<?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>Fri, 02 Oct 2026 18:54:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74438 — crypto: sun4i-ss - Remove insecure and unused rng_alg</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74438</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: sun4i-ss - Remove insecure and unused rng_alg&lt;/p&gt;
&lt;p&gt;Remove sun4i_ss_rng, as it is insecure and unused:&lt;/p&gt;
&lt;p&gt;- It has multiple vulnerabilities.  sun4i_ss_prng_seed() is missing
  locking and has a buffer overflow.  sun4i_ss_prng_generate() fails to
  fill the entire buffer with cryptographic random bytes, because it
  rounds the destination length down and also doesn&amp;#39;t actually wait for
  the hardware to be ready before pulling bytes from it.&lt;/p&gt;
&lt;p&gt;- No user of this code is known.  It&amp;#39;s usable only theoretically via the
  &amp;#34;rng&amp;#34; algorithm type of AF_ALG.  But userspace actually just uses the
  actual Linux RNG (/dev/random etc) instead.  And rng_algs don&amp;#39;t
  contribute entropy to the actual Linux RNG either.  (This may have
  been confused with hwrng, which does contribute entropy.)&lt;/p&gt;
&lt;p&gt;The sun4i_ss_prng_seed() buffer overflow was reported by Tianchu Chen
and discovered by Atuin - Automated Vulnerability Discovery Engine&lt;/p&gt;
&lt;p&gt;There&amp;#39;s no point in fixing all these vulnerabilities individually when
this is unused code, so let&amp;#39;s just remove it.&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: sun4i-ss - Remove insecure and unused rng_alg&lt;/p&gt;
&lt;p&gt;Remove sun4i_ss_rng, as it is insecure and unused:&lt;/p&gt;
&lt;p&gt;- It has multiple vulnerabilities.  sun4i_ss_prng_seed() is missing
  locking and has a buffer overflow.  sun4i_ss_prng_generate() fails to
  fill the entire buffer with cryptographic random bytes, because it
  rounds the destination length down and also doesn&amp;#39;t actually wait for
  the hardware to be ready before pulling bytes from it.&lt;/p&gt;
&lt;p&gt;- No user of this code is known.  It&amp;#39;s usable only theoretically via the
  &amp;#34;rng&amp;#34; algorithm type of AF_ALG.  But userspace actually just uses the
  actual Linux RNG (/dev/random etc) instead.  And rng_algs don&amp;#39;t
  contribute entropy to the actual Linux RNG either.  (This may have
  been confused with hwrng, which does contribute entropy.)&lt;/p&gt;
&lt;p&gt;The sun4i_ss_prng_seed() buffer overflow was reported by Tianchu Chen
and discovered by Atuin - Automated Vulnerability Discovery Engine&lt;/p&gt;
&lt;p&gt;There&amp;#39;s no point in fixing all these vulnerabilities individually when
this is unused code, so let&amp;#39;s just remove it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74438</guid>
    </item>
  </channel>
</rss>
