{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50887 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50887 is a memory corruption vulnerability in Linux, published on 30 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2022-50887 and fix it if it is affected.\n\nWhat it is: CVE-2022-50887 is a memory corruption vulnerability in Linux, published on 30 Dec 2025. \nExploitation: There is no known exploitation of CVE-2022-50887 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-50887/ (Markdown: https://insights.sbomify.com/CVE-2022-50887/index.md)","id":"CVE-2022-50887","markdown":"https://insights.sbomify.com/CVE-2022-50887/index.md","name":"CVE-2022-50887","record":{"aliases":["DEBIAN-CVE-2022-50887","GHSA-jpr9-mqf4-fm6w","UBUNTU-CVE-2022-50887"],"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 refcount imbalance in the Linux kernel regulator core can cause memory leaks, potentially leading to 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\nregulator: core: fix unbalanced of node refcount in regulator_dev_lookup()\n\nI got the the following report:\n\n  OF: ERROR: memory leak, expected refcount 1 instead of 2,\n  of_node_get()/of_node_put() unbalanced - destroy cset entry:\n  attach overlay node /i2c/pmic@62/regulators/exten\n\nIn of_get_regulator(), the node is returned from of_parse_phandle()\nwith refcount incremented, after using it, of_node_put() need be called.","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":"regulator: core: fix unbalanced of node refcount in regulator_dev_lookup()","id":"CVE-2022-50887","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":"remoteproc: qcom: q6v5: Fix potential null-ptr-deref in q6v5_wcss_init_mmio()","id":"CVE-2022-50888"},"packages":[],"prev":{"headline":"mmc: toshsd: fix return value check of mmc_add_host()","id":"CVE-2022-50886"},"products":["Linux"],"published":"2025-12-30","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 refcount imbalance in the Linux kernel regulator core can cause memory leaks, potentially leading to denial of service.","url":"https://insights.sbomify.com/CVE-2022-50887/"}