{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50557 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50557 is a memory corruption vulnerability in Linux, published on 22 Oct 2025."},"fix_prompt":"Check this codebase for CVE-2022-50557 and fix it if it is affected.\n\nWhat it is: CVE-2022-50557 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. \nExploitation: There is no known exploitation of CVE-2022-50557 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-50557/ (Markdown: https://insights.sbomify.com/CVE-2022-50557/index.md)","id":"CVE-2022-50557","markdown":"https://insights.sbomify.com/CVE-2022-50557/index.md","name":"CVE-2022-50557","record":{"aliases":["DEBIAN-CVE-2022-50557","GHSA-hjpq-cx8h-9x2f","UBUNTU-CVE-2022-50557"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A memory leak in the Linux kernel Thunderbay pinctrl 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\npinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions()\n\nThe thunderbay_add_functions() will free memory of thunderbay_funcs\nwhen everything is ok, but thunderbay_funcs will not be freed when\nthunderbay_add_functions() fails, then there will be a memory leak,\nso we need to add kfree() when thunderbay_add_functions() fails to\nfix it.\n\nIn addition, doing some cleaner works, moving kfree(funcs) from\nthunderbay_add_functions() to thunderbay_build_functions().","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":"pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions()","id":"CVE-2022-50557","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode","id":"CVE-2022-50558"},"packages":[],"prev":{"headline":"drm: Fix potential null-ptr-deref due to drmm_mode_config_init()","id":"CVE-2022-50556"},"products":["Linux"],"published":"2025-10-22","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 Thunderbay pinctrl driver can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2022-50557/"}