{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50637 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50637 is a memory corruption vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-50637 and fix it if it is affected.\n\nWhat it is: CVE-2022-50637 is a memory corruption vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-50637 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-50637/ (Markdown: https://insights.sbomify.com/CVE-2022-50637/index.md)","id":"CVE-2022-50637","markdown":"https://insights.sbomify.com/CVE-2022-50637/index.md","name":"CVE-2022-50637","record":{"aliases":["DEBIAN-CVE-2022-50637","GHSA-3p55-pgh8-7x5v","UBUNTU-CVE-2022-50637"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A memory leak in the Linux kernel's Qualcomm cpufreq driver can lead to 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\ncpufreq: qcom-hw: Fix memory leak in qcom_cpufreq_hw_read_lut()\n\nIf \"cpu_dev\" fails to get opp table in qcom_cpufreq_hw_read_lut(),\nthe program will return, resulting in \"table\" resource is not released.","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":"cpufreq: qcom-hw: Fix memory leak in qcom_cpufreq_hw_read_lut()","id":"CVE-2022-50637","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"ext4: fix bug_on in __es_tree_search caused by bad boot loader inode","id":"CVE-2022-50638"},"packages":[],"prev":{"headline":"PCI: Fix pci_device_is_present() for VFs by checking PF","id":"CVE-2022-50636"},"products":["Linux"],"published":"2025-12-09","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 memory leak in the Linux kernel's Qualcomm cpufreq driver can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2022-50637/"}