CVE-2022-50731
published 2025-12-24CVE-2022-50731: In the Linux kernel, the following vulnerability has been resolved: crypto: akcipher - default implementation for setting a private key Changes from v1: *…
PriorityP424medium5.5
EPSS
0.22%
12.5th percentile
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.Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.3-1 (bookworm) | linux 6.0.3-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 78a0324f4a5328088fea9426cfe1d1851276c475 < 95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e | 95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e |
| linux | linux | >= 78a0324f4a5328088fea9426cfe1d1851276c475 < a1354bdd191d533211b7cb723aa76a66f516f197 | a1354bdd191d533211b7cb723aa76a66f516f197 |
| linux | linux | >= 78a0324f4a5328088fea9426cfe1d1851276c475 < 779a9930f3e152c82699feb389a0e6d6644e747e | 779a9930f3e152c82699feb389a0e6d6644e747e |
| linux | linux | >= 78a0324f4a5328088fea9426cfe1d1851276c475 < 85bc736a18b872f54912e8bb70682d11770aece0 | 85bc736a18b872f54912e8bb70682d11770aece0 |
| linux | linux | >= 78a0324f4a5328088fea9426cfe1d1851276c475 < f9058178597059d6307efe96a7916600f8ede08c | f9058178597059d6307efe96a7916600f8ede08c |
| linux | linux | >= 78a0324f4a5328088fea9426cfe1d1851276c475 < bc155c6c188c2f0c5749993b1405673d25a80389 | bc155c6c188c2f0c5749993b1405673d25a80389 |
| linux | linux_kernel | >= 0 < 5.10.158-1 | 5.10.158-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 5.11.0 < 5.15.75 | 5.15.75 |
| linux | linux_kernel | >= 5.16.0 < 5.19.17 | 5.19.17 |
| linux | linux_kernel | >= 5.2.0 < 5.4.220 | 5.4.220 |
| linux | linux_kernel | >= 5.20.0 < 6.0.3 | 6.0.3 |
| linux | linux_kernel | >= 5.5.0 < 5.10.150 | 5.10.150 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Linux Kernel up to 6.0.2 set_pub_key null pointer dereference (Nessus ID 279939 / WID-SEC-2025-2929)
vuldb·2026-04-21
CVE-2022-50731 [CRITICAL] Linux Kernel up to 6.0.2 set_pub_key null pointer dereference (Nessus ID 279939 / WID-SEC-2025-2929)
A vulnerability marked as critical has been reported in Linux Kernel up to 5.4.219/5.10.149/5.15.74/5.19.16/6.0.2. The affected element is the function set_pub_key. This manipulation causes null pointer dereference.
This vulnerability is registered as CVE-2022-50731. The attack requires access to the local network. No exploit is available.
It is suggested to upgrade the affected component.
OSV
crypto: akcipher - default implementation for setting a private key
osv·2025-12-24
CVE-2022-50731 crypto: akcipher - default implementation for setting a private key
crypto: akcipher - default implementation for setting a private key
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 ca
OSV
CVE-2022-50731: In the Linux kernel, the following vulnerability has been resolved: crypto: akcipher - default implementation for setting a private key Changes from v
osv·2025-12-24
CVE-2022-50731 CVE-2022-50731: In the Linux kernel, the following vulnerability has been resolved: crypto: akcipher - default implementation for setting a private key Changes from v
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 (a
GHSA
GHSA-26jg-99jv-7wgw: In the Linux kernel, the following vulnerability has been resolved:
crypto: akcipher - default implementation for setting a private key
Changes from
ghsa_unreviewed·2025-12-24
CVE-2022-50731 GHSA-26jg-99jv-7wgw: In the Linux kernel, the following vulnerability has been resolved:
crypto: akcipher - default implementation for setting a private key
Changes from
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 transfo
Red Hat
kernel: Linux kernel: Denial of Service in akcipher due to missing set_priv_key stub
vendor_redhat·2025-12-24·CVSS 5.5
CVE-2022-50731 [MEDIUM] CWE-476 kernel: Linux kernel: Denial of Service in akcipher due to missing set_priv_key stub
kernel: Linux kernel: Denial of Service in akcipher due to missing set_priv_key stub
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
Debian
CVE-2022-50731: linux - In the Linux kernel, the following vulnerability has been resolved: crypto: akc...
vendor_debian·2022
CVE-2022-50731 CVE-2022-50731: linux - In the Linux kernel, the following vulnerability has been resolved: crypto: akc...
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 (a
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2022-50731 kernel: Linux kernel: Denial of Service in akcipher due to missing set_priv_key stub
bugzilla·2025-12-24
CVE-2022-50731 [MEDIUM] CVE-2022-50731 kernel: Linux kernel: Denial of Service in akcipher due to missing set_priv_key stub
CVE-2022-50731 kernel: Linux kernel: Denial of Service in akcipher due to missing set_priv_key stub
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, be
Wiz
CVE-2022-50731 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2022-50731 CVE-2022-50731 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2022-50731 :
Linux Kernel vulnerability analysis and mitigation
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 ca
https://git.kernel.org/stable/c/779a9930f3e152c82699feb389a0e6d6644e747ehttps://git.kernel.org/stable/c/85bc736a18b872f54912e8bb70682d11770aece0https://git.kernel.org/stable/c/95c4e20adc3ea00d1594a2a05d9b187ed12ffa8ehttps://git.kernel.org/stable/c/a1354bdd191d533211b7cb723aa76a66f516f197https://git.kernel.org/stable/c/bc155c6c188c2f0c5749993b1405673d25a80389https://git.kernel.org/stable/c/f9058178597059d6307efe96a7916600f8ede08c
2025-12-24
Published