{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50731 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50731 is a vulnerability in Linux, published on 24 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2022-50731 and fix it if it is affected.\n\nWhat it is: CVE-2022-50731 is a vulnerability in Linux, published on 24 Dec 2025. \nExploitation: There is no known exploitation of CVE-2022-50731 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50731/ (Markdown: https://insights.sbomify.com/CVE-2022-50731/index.md)","id":"CVE-2022-50731","markdown":"https://insights.sbomify.com/CVE-2022-50731/index.md","name":"CVE-2022-50731","record":{"aliases":["DEBIAN-CVE-2022-50731","GHSA-26jg-99jv-7wgw","UBUNTU-CVE-2022-50731"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A null pointer dereference in the Linux kernel crypto subsystem allows local attackers to cause a denial of service by triggering a crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: akcipher - default implementation for setting a private key\n\nChanges from v1:\n  * removed the default implementation from set_pub_key: it is assumed that\n    an implementation must always have this callback defined as there are\n    no use case for an algorithm, which doesn't need a public key\n\nMany akcipher implementations (like ECDSA) support only signature\nverifications, so they don't have all callbacks defined.\n\nCommit 78a0324f4a53 (\"crypto: akcipher - default implementations for\nrequest callbacks\") introduced default callbacks for sign/verify\noperations, which just return an error code.\n\nHowever, these are not enough, because before calling sign the caller would\nlikely call set_priv_key first on the instantiated transform (as the\nin-kernel testmgr does). This function does not have a default stub, so the\nkernel crashes, when trying to set a private key on an akcipher, which\ndoesn't support signature generation.\n\nI've noticed this, when trying to add a KAT vector for ECDSA signature to\nthe testmgr.\n\nWith this patch the testmgr returns an error in dmesg (as it should)\ninstead of crashing the kernel NULL ptr dereference.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"crypto: akcipher - default implementation for setting a private key","id":"CVE-2022-50731","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":6,"next":{"headline":"staging: rtl8192u: Fix use after free in ieee80211_rx()","id":"CVE-2022-50732"},"packages":[],"prev":{"headline":"ext4: silence the warning when evicting inode with dioread_nolock","id":"CVE-2022-50730"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel crypto subsystem allows local attackers to cause a denial of service by triggering a crash.","url":"https://insights.sbomify.com/CVE-2022-50731/"}