https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 17:46:53 +0000 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/euvd-2026-311405 EUVD-2026-311405 https://cve.radiocsirt.org/vuln/euvd-2026-311405 https://cve.radiocsirt.org/vuln/fkie_cve-2022-50731 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: akcipher - default implementation for setting a private key</p> <p>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&#39;t need a public key</p> <p>Many akcipher implementations (like ECDSA) support only signature verifications, so they don&#39;t have all callbacks defined.</p> <p>Commit 78a0324f4a53 (&#34;crypto: akcipher - default implementations for request callbacks&#34;) introduced default callbacks for sign/verify operations, which just return an error code.</p> <p>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&#39;t support signature generation.</p> <p>I&#39;ve noticed this, when trying to add a KAT vector for ECDSA signature to the testmgr.</p> <p>With this patch the testmgr returns an error in dmesg (as it should) instead of crashing the kernel NULL ptr dereference.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: akcipher - default implementation for setting a private key</p> <p>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&#39;t need a public key</p> <p>Many akcipher implementations (like ECDSA) support only signature verifications, so they don&#39;t have all callbacks defined.</p> <p>Commit 78a0324f4a53 (&#34;crypto: akcipher - default implementations for request callbacks&#34;) introduced default callbacks for sign/verify operations, which just return an error code.</p> <p>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&#39;t support signature generation.</p> <p>I&#39;ve noticed this, when trying to add a KAT vector for ECDSA signature to the testmgr.</p> <p>With this patch the testmgr returns an error in dmesg (as it should) instead of crashing the kernel NULL ptr dereference.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-50731 https://cve.radiocsirt.org/vuln/ghsa-26jg-99jv-7wgw <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: akcipher - default implementation for setting a private key</p> <p>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&#39;t need a public key</p> <p>Many akcipher implementations (like ECDSA) support only signature verifications, so they don&#39;t have all callbacks defined.</p> <p>Commit 78a0324f4a53 (&#34;crypto: akcipher - default implementations for request callbacks&#34;) introduced default callbacks for sign/verify operations, which just return an error code.</p> <p>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&#39;t support signature generation.</p> <p>I&#39;ve noticed this, when trying to add a KAT vector for ECDSA signature to the testmgr.</p> <p>With this patch the testmgr returns an error in dmesg (as it should) instead of crashing the kernel NULL ptr dereference.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: akcipher - default implementation for setting a private key</p> <p>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&#39;t need a public key</p> <p>Many akcipher implementations (like ECDSA) support only signature verifications, so they don&#39;t have all callbacks defined.</p> <p>Commit 78a0324f4a53 (&#34;crypto: akcipher - default implementations for request callbacks&#34;) introduced default callbacks for sign/verify operations, which just return an error code.</p> <p>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&#39;t support signature generation.</p> <p>I&#39;ve noticed this, when trying to add a KAT vector for ECDSA signature to the testmgr.</p> <p>With this patch the testmgr returns an error in dmesg (as it should) instead of crashing the kernel NULL ptr dereference.</p> https://cve.radiocsirt.org/vuln/ghsa-26jg-99jv-7wgw https://cve.radiocsirt.org/vuln/suse-su-2026:0263-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:0263-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50731 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 128 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: crypto: akcipher - default implementation for setting a private key 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&#39;t need a public key Many akcipher implementations (like ECDSA) support only signature verifications, so they don&#39;t have all callbacks defined. Commit 78a0324f4a53 (&#34;crypto: akcipher - default implementations for request callbacks&#34;) introduced default callbacks for sign/verify operations, which just return an error code. 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&#39;t support signature generation. I&#39;ve noticed this, when trying to add a KAT vector for ECDSA signature to the testmgr. With this patch the testmgr returns an error in dmesg (as it should) instead of crashing the kernel NULL ptr dereference.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 128 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: crypto: akcipher - default implementation for setting a private key 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&#39;t need a public key Many akcipher implementations (like ECDSA) support only signature verifications, so they don&#39;t have all callbacks defined. Commit 78a0324f4a53 (&#34;crypto: akcipher - default implementations for request callbacks&#34;) introduced default callbacks for sign/verify operations, which just return an error code. 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&#39;t support signature generation. I&#39;ve noticed this, when trying to add a KAT vector for ECDSA signature to the testmgr. With this patch the testmgr returns an error in dmesg (as it should) instead of crashing the kernel NULL ptr dereference.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50731 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929 <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929