{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50575 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50575 is a denial of service 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-50575 and fix it if it is affected.\n\nWhat it is: CVE-2022-50575 is a denial of service 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-50575 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-50575/ (Markdown: https://insights.sbomify.com/CVE-2022-50575/index.md)","id":"CVE-2022-50575","markdown":"https://insights.sbomify.com/CVE-2022-50575/index.md","name":"CVE-2022-50575","record":{"aliases":["DEBIAN-CVE-2022-50575","GHSA-jhf6-8mmm-jxfr","UBUNTU-CVE-2022-50575"],"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":"low_privilege","summary":"A local attacker can trigger excessive kernel warnings and potential resource exhaustion via the Xen privcmd interface by requesting large memory allocations.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nxen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()\n\nAs 'kdata.num' is user-controlled data, if user tries to allocate\nmemory larger than(\u003e=) MAX_ORDER, then kcalloc() will fail, it\ncreates a stack trace and messes up dmesg with a warning.\n\nCall trace:\n-\u003e privcmd_ioctl\n--\u003e privcmd_ioctl_mmap_resource\n\nAdd __GFP_NOWARN in order to avoid too large allocation warning.\nThis is detected by static analysis using smatch.","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":"xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()","id":"CVE-2022-50575","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":7,"next":{"headline":"serial: pch: Fix PCI device refcount leak in pch_request_dma()","id":"CVE-2022-50576"},"packages":[],"prev":{"headline":"drm/omap: dss: Fix refcount leak bugs","id":"CVE-2022-50574"},"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 local attacker can trigger excessive kernel warnings and potential resource exhaustion via the Xen privcmd interface by requesting large memory allocations.","url":"https://insights.sbomify.com/CVE-2022-50575/"}