{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50776 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50776 is a memory corruption vulnerability in Linux, published on 24 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2022-50776 and fix it if it is affected.\n\nWhat it is: CVE-2022-50776 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. \nExploitation: There is no known exploitation of CVE-2022-50776 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-50776/ (Markdown: https://insights.sbomify.com/CVE-2022-50776/index.md)","id":"CVE-2022-50776","markdown":"https://insights.sbomify.com/CVE-2022-50776/index.md","name":"CVE-2022-50776","record":{"aliases":["DEBIAN-CVE-2022-50776","GHSA-86q8-vcjj-g3x5","UBUNTU-CVE-2022-50776"],"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's ST clock 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\nclk: st: Fix memory leak in st_of_quadfs_setup()\n\nIf st_clk_register_quadfs_pll() fails, @lock should be freed before goto\n@err_exit, otherwise will cause meory leak issue, fix it.","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":"clk: st: Fix memory leak in st_of_quadfs_setup()","id":"CVE-2022-50776","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":9,"next":{"headline":"net: phy: xgmiitorgmii: Fix refcount leak in xgmiitorgmii_probe","id":"CVE-2022-50777"},"packages":[],"prev":{"headline":"RDMA/hns: Fix refcount leak in hns_roce_mmap","id":"CVE-2022-50775"},"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 memory leak in the Linux kernel's ST clock driver can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2022-50776/"}