{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50574 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50574 is a memory corruption vulnerability in Linux, published on 22 Oct 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-50574 and fix it if it is affected.\n\nWhat it is: CVE-2022-50574 is a memory corruption vulnerability in Linux, published on 22 Oct 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-50574 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-50574/ (Markdown: https://insights.sbomify.com/CVE-2022-50574/index.md)","id":"CVE-2022-50574","markdown":"https://insights.sbomify.com/CVE-2022-50574/index.md","name":"CVE-2022-50574","record":{"aliases":["DEBIAN-CVE-2022-50574","GHSA-p683-q2j4-xm32","UBUNTU-CVE-2022-50574"],"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 refcount leak in the Linux kernel's OMAP display subsystem can lead to memory 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\ndrm/omap: dss: Fix refcount leak bugs\n\nIn dss_init_ports() and __dss_uninit_ports(), we should call\nof_node_put() for the reference returned by of_graph_get_port_by_id()\nin fail path or when it is not used anymore.","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":"drm/omap: dss: Fix refcount leak bugs","id":"CVE-2022-50574","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":6,"next":{"headline":"xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()","id":"CVE-2022-50575"},"packages":[],"prev":{"headline":"wifi: mt76: mt7915: fix mt7915_rate_txpower_get() resource leaks","id":"CVE-2022-50573"},"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 refcount leak in the Linux kernel's OMAP display subsystem can lead to memory exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2022-50574/"}