<?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 17:14:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50731 — crypto: akcipher - default implementation for setting a private key</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50731</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: akcipher - default implementation for setting a private key&lt;/p&gt;
&lt;p&gt;Changes from v1:
  * removed the default implementation from set_pub_key: it is assumed that
    an implementation must always have this callback defined as there are
    no use case for an algorithm, which doesn&amp;#39;t need a public key&lt;/p&gt;
&lt;p&gt;Many akcipher implementations (like ECDSA) support only signature
verifications, so they don&amp;#39;t have all callbacks defined.&lt;/p&gt;
&lt;p&gt;Commit 78a0324f4a53 (&amp;#34;crypto: akcipher - default implementations for
request callbacks&amp;#34;) introduced default callbacks for sign/verify
operations, which just return an error code.&lt;/p&gt;
&lt;p&gt;However, these are not enough, because before calling sign the caller would
likely call set_priv_key first on the instantiated transform (as the
in-kernel testmgr does). This function does not have a default stub, so the
kernel crashes, when trying to set a private key on an akcipher, which
doesn&amp;#39;t support signature generation.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve noticed this, when trying to add a KAT vector for ECDSA signature to
the testmgr.&lt;/p&gt;
&lt;p&gt;With this patch the testmgr returns an error in dmesg (as it should)
instead of crashing the kernel NULL ptr dereference.&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: akcipher - default implementation for setting a private key&lt;/p&gt;
&lt;p&gt;Changes from v1:
  * removed the default implementation from set_pub_key: it is assumed that
    an implementation must always have this callback defined as there are
    no use case for an algorithm, which doesn&amp;#39;t need a public key&lt;/p&gt;
&lt;p&gt;Many akcipher implementations (like ECDSA) support only signature
verifications, so they don&amp;#39;t have all callbacks defined.&lt;/p&gt;
&lt;p&gt;Commit 78a0324f4a53 (&amp;#34;crypto: akcipher - default implementations for
request callbacks&amp;#34;) introduced default callbacks for sign/verify
operations, which just return an error code.&lt;/p&gt;
&lt;p&gt;However, these are not enough, because before calling sign the caller would
likely call set_priv_key first on the instantiated transform (as the
in-kernel testmgr does). This function does not have a default stub, so the
kernel crashes, when trying to set a private key on an akcipher, which
doesn&amp;#39;t support signature generation.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve noticed this, when trying to add a KAT vector for ECDSA signature to
the testmgr.&lt;/p&gt;
&lt;p&gt;With this patch the testmgr returns an error in dmesg (as it should)
instead of crashing the kernel NULL ptr dereference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50731</guid>
    </item>
  </channel>
</rss>
