{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50734 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50734 is a memory corruption vulnerability in Linux, published on 24 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2022-50734 and fix it if it is affected.\n\nWhat it is: CVE-2022-50734 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. \nExploitation: There is no known exploitation of CVE-2022-50734 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-50734/ (Markdown: https://insights.sbomify.com/CVE-2022-50734/index.md)","id":"CVE-2022-50734","markdown":"https://insights.sbomify.com/CVE-2022-50734/index.md","name":"CVE-2022-50734","record":{"aliases":["DEBIAN-CVE-2022-50734","GHSA-p8g3-3wvp-3jxw","UBUNTU-CVE-2022-50734"],"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 memory leak in the Linux kernel nvmem core allows local attackers to cause resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nnvmem: core: Fix memleak in nvmem_register()\n\ndev_set_name will alloc memory for nvmem-\u003edev.kobj.name in\nnvmem_register, when nvmem_validate_keepouts failed, nvmem's\nmemory will be freed and return, but nobody will free memory\nfor nvmem-\u003edev.kobj.name, there will be memleak, so moving\nnvmem_validate_keepouts() after device_register() and let\nthe device core deal with cleaning name in error cases.","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":"nvmem: core: Fix memleak in nvmem_register()","id":"CVE-2022-50734","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"wifi: mt76: do not run mt76u_status_worker if the device is not running","id":"CVE-2022-50735"},"packages":[],"prev":{"headline":"usb: idmouse: fix an uninit-value in idmouse_open","id":"CVE-2022-50733"},"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-23","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel nvmem core allows local attackers to cause resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2022-50734/"}