CVE-2022-50731

crypto: akcipher - default implementation for setting a private key

N/A
Published: December 24, 2025 at 12:22 PM UTC
Updated: June 17, 2026 at 05:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.2 ≤ v < 5.10.1505.2 ≤ v < 5.15.755.2 ≤ v < 5.19.175.2 ≤ v < 5.4.2205.2 ≤ v < 6.0.35.2 ≤ v < 6.15.278a0324f4a5328088fea9426cfe1d1851276c475
Vendor states this is fixed in 779a9930f3e152c82699feb389a0e6d6644e747e (fixed)
Vendor states this is fixed in 85bc736a18b872f54912e8bb70682d11770aece0 (fixed)
Vendor states this is fixed in 95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e (fixed)
Vendor states this is fixed in a1354bdd191d533211b7cb723aa76a66f516f197 (fixed)
Vendor states this is fixed in bc155c6c188c2f0c5749993b1405673d25a80389 (fixed)
Vendor states this is fixed in f9058178597059d6307efe96a7916600f8ede08c (fixed)
Vendor states this is fixed in 5.10.150 (unaffected)
Vendor states this is fixed in 5.15.75 (unaffected)
Vendor states this is fixed in 5.19.17 (unaffected)
Vendor states this is fixed in 5.2 (unaffected)
Vendor states this is fixed in 5.4.220 (unaffected)
Vendor states this is fixed in 6.0.3 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card