CVE-2022-50731: crypto: akcipher - default implementation for setting a private key
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Fixed version: Linux Linux 779a9930f3e152c82699feb389a0e6d6644e747e, 85bc736a18b872f54912e8bb70682d11770aece0, 95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e.
Low priority for now. Upgrade to Linux Linux 779a9930f3e152c82699feb389a0e6d6644e747e, 85bc736a18b872f54912e8bb70682d11770aece0, 95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.2affected
- 78a0324f4a5328088fea9426cfe1d1851276c475 and later · before 95c4e20adc3ea00d1594a2a05d9b187ed12ffa8eaffected · git
- 78a0324f4a5328088fea9426cfe1d1851276c475 and later · before a1354bdd191d533211b7cb723aa76a66f516f197affected · git
- 78a0324f4a5328088fea9426cfe1d1851276c475 and later · before 779a9930f3e152c82699feb389a0e6d6644e747eaffected · git
- 78a0324f4a5328088fea9426cfe1d1851276c475 and later · before 85bc736a18b872f54912e8bb70682d11770aece0affected · git
- 78a0324f4a5328088fea9426cfe1d1851276c475 and later · before f9058178597059d6307efe96a7916600f8ede08caffected · git
- 78a0324f4a5328088fea9426cfe1d1851276c475 and later · before bc155c6c188c2f0c5749993b1405673d25a80389affected · git
- before 5.2not affected · semver
- 5.4.220 and later · up to and including 5.4.*not affected · semver
- 5.10.150 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.3-1 | 6.0.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-50729Dec 24, 2025 · ksmbd: Fix resource leak in ksmbd_session_rpc_open()0Monitor
- ← EarlierCVE-2022-50730Dec 24, 2025 · ext4: silence the warning when evicting inode with dioread_nolock0Monitor
- Later →CVE-2022-50732Dec 24, 2025 · staging: rtl8192u: Fix use after free in ieee80211_rx()35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 779a9930f3e152c82699feb389a0e6d6644e747e | Vendor (CNA) |
| Linux Linux | 85bc736a18b872f54912e8bb70682d11770aece0 | Vendor (CNA) |
| Linux Linux | 95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e | Vendor (CNA) |
| Linux Linux | a1354bdd191d533211b7cb723aa76a66f516f197 | Vendor (CNA) |
| Linux Linux | bc155c6c188c2f0c5749993b1405673d25a80389 | Vendor (CNA) |
| Linux Linux | f9058178597059d6307efe96a7916600f8ede08c | Vendor (CNA) |
| debian:linux | 6.0.3-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/85bc736a18b872f54912e8bb70682d11770aece0
- git.kernel.org/stable/c/95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e
- git.kernel.org/stable/c/a1354bdd191d533211b7cb723aa76a66f516f197
- git.kernel.org/stable/c/bc155c6c188c2f0c5749993b1405673d25a80389
- git.kernel.org/stable/c/f9058178597059d6307efe96a7916600f8ede08c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.