Kernel crash via missing akcipher private-key stub
Published Dec 24, 2025 · Updated Dec 24, 2025
Affected Linux kernel branches starting at 5.2 allow local users to crash the kernel through an unsupported akcipher private-key operation. In crypto/akcipher.c, set_priv_key lacks a default error stub, so a transform that implements verification but not signing calls a NULL callback. A local user must reach the kernel asymmetric-key API and select such an algorithm; the bounded consequence is a host-wide kernel crash.
Summary
What happened
Affected Linux kernel branches starting at 5.2 allow local users to crash the kernel through an unsupported akcipher private-key operation. In crypto/akcipher.c, set_priv_key lacks a default error stub, so a transform that implements verification but not signing calls a NULL callback. A local user must reach the kernel asymmetric-key API and select such an algorithm; the bounded consequence is a host-wide kernel crash.
The record
- CVE
- CVE-2022-50731
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.2
- Affected versionversion=78a0324f4a5328088fea9426cfe1d1851276c475 <779a9930f3e152c82699feb389a0e6d6644e747e
- Affected versionversion=78a0324f4a5328088fea9426cfe1d1851276c475 <85bc736a18b872f54912e8bb70682d11770aece0
- Affected versionversion=78a0324f4a5328088fea9426cfe1d1851276c475 <95c4e20adc3ea00d1594a2a05d9b187ed12ffa8e
- Affected versionversion=78a0324f4a5328088fea9426cfe1d1851276c475 <a1354bdd191d533211b7cb723aa76a66f516f197
- Affected versionversion=78a0324f4a5328088fea9426cfe1d1851276c475 <bc155c6c188c2f0c5749993b1405673d25a80389
- Affected versionversion=78a0324f4a5328088fea9426cfe1d1851276c475 <f9058178597059d6307efe96a7916600f8ede08c
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo