CVE-2022-50731

Unknown

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.

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedDec 24, 2025
First seenDec 24, 2025

How to fix

Update
  • Linux Linux95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e, a1354bdd191d533211b7cb723aa76a66f516f197, 779a9930f3e152c82699feb389a0e6d6644e747e, 85bc736a18b872f54912e8bb70682d11770aece0, f9058178597059d6307efe96a7916600f8ede08c, bc155c6c188c2f0c5749993b1405673d25a80389 or later

Affected products

ProductAffected versionsFixed in
Linux Linux78a0324f4a5328088fea9426cfe1d1851276c475 ≤ v < 95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e, 78a0324f4a5328088fea9426cfe1d1851276c475 ≤ v < a1354bdd191d533211b7cb723aa76a66f516f197, 78a0324f4a5328088fea9426cfe1d1851276c475 ≤ v < 779a9930f3e152c82699feb389a0e6d6644e747e, 78a0324f4a5328088fea9426cfe1d1851276c475 ≤ v < 85bc736a18b872f54912e8bb70682d11770aece0, 78a0324f4a5328088fea9426cfe1d1851276c475 ≤ v < f9058178597059d6307efe96a7916600f8ede08c, 78a0324f4a5328088fea9426cfe1d1851276c475 ≤ v < bc155c6c188c2f0c5749993b1405673d25a80389, 5.295c4e20adc3ea00d1594a2a05d9b187ed12ffa8e, a1354bdd191d533211b7cb723aa76a66f516f197, 779a9930f3e152c82699feb389a0e6d6644e747e, 85bc736a18b872f54912e8bb70682d11770aece0, f9058178597059d6307efe96a7916600f8ede08c, bc155c6c188c2f0c5749993b1405673d25a80389

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.