CVE-2022-50731 Details
Description
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't need a public key Many akcipher implementations (like ECDSA) support only signature verifications, so they don't have all callbacks defined. Commit 78a0324f4a53 ("crypto: akcipher - default implementations for request callbacks") 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't support signature generation. I'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.
A vulnerability exists in the Linux kernel's crypto akcipher implementation, specifically in how private keys are managed. This issue arises because certain akcipher algorithms, like ECDSA, only perform signature verification and do not define all necessary callback functions. When a private key is set on such an algorithm, the kernel can crash due to a null pointer dereference. The vulnerability has been addressed by modifying the akcipher registration process to ensure that the set_priv_key callback is properly defined, preventing the kernel from crashing when handling private keys for algorithms that do not support signature generation.
The vulnerability has been fixed in the Linux kernel by updating the akcipher registration process to include a default implementation for the set_priv_key callback, ensuring that private keys can be handled correctly without causing a crash.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 24, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/779a9930f3e152c82699feb389a0e6d6644e747e | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/85bc736a18b872f54912e8bb70682d11770aece0 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/a1354bdd191d533211b7cb723aa76a66f516f197 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/bc155c6c188c2f0c5749993b1405673d25a80389 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/f9058178597059d6307efe96a7916600f8ede08c | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 10, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 24, 2025 | New CVE Received | kernel.org |
Volerion