CVE-2022-50731crypto: akcipher - default implementation for setting a private key
- —Not scoredno CVSS score yet
- 0.25%Exploitation in 30 daysEPSS · top 83% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.25% · top 83% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 78a0324f4a5328088fea9426cfe1d1851276c475 – < 95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e
- affected 78a0324f4a5328088fea9426cfe1d1851276c475 – < a1354bdd191d533211b7cb723aa76a66f516f197
- affected 78a0324f4a5328088fea9426cfe1d1851276c475 – < 779a9930f3e152c82699feb389a0e6d6644e747e
- affected 78a0324f4a5328088fea9426cfe1d1851276c475 – < 85bc736a18b872f54912e8bb70682d11770aece0
- affected 78a0324f4a5328088fea9426cfe1d1851276c475 – < f9058178597059d6307efe96a7916600f8ede08c
- affected 78a0324f4a5328088fea9426cfe1d1851276c475 – < bc155c6c188c2f0c5749993b1405673d25a80389
- affected 5.2
- unaffected < 5.2
- unaffected 5.4.220 – ≤ 5.4.*
- unaffected 5.10.150 – ≤ 5.10.*
- unaffected 5.15.75 – ≤ 5.15.*
- unaffected 5.19.17 – ≤ 5.19.*
- unaffected 6.0.3 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References
References6
- https://git.kernel.org/stable/c/95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e (opens in a new tab)
- https://git.kernel.org/stable/c/a1354bdd191d533211b7cb723aa76a66f516f197 (opens in a new tab)
- https://git.kernel.org/stable/c/779a9930f3e152c82699feb389a0e6d6644e747e (opens in a new tab)
- https://git.kernel.org/stable/c/85bc736a18b872f54912e8bb70682d11770aece0 (opens in a new tab)
- https://git.kernel.org/stable/c/f9058178597059d6307efe96a7916600f8ede08c (opens in a new tab)
- https://git.kernel.org/stable/c/bc155c6c188c2f0c5749993b1405673d25a80389 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-55758 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-50731)Record last updated .