{"answers":{"affected":"1 open source package ship an affected version, including Kernel.","exploited":"There is no known exploitation of GSD-2022-1000562 in the wild and no public exploit code.","fix":"No fix has been published for GSD-2022-1000562 yet. Limit exposure of the affected software until one is available.","what":"GSD-2022-1000562 is a memory corruption vulnerability in Kernel, published on 27 Feb 2022."},"fix_prompt":"Check this codebase for GSD-2022-1000562 and fix it if it is affected.\n\nWhat it is: GSD-2022-1000562 is a memory corruption vulnerability in Kernel, published on 27 Feb 2022. \nExploitation: There is no known exploitation of GSD-2022-1000562 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Kernel (Linux): affected all versions; no fix listed\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/GSD-2022-1000562/ (Markdown: https://insights.sbomify.com/GSD-2022-1000562/index.md)","id":"GSD-2022-1000562","markdown":"https://insights.sbomify.com/GSD-2022-1000562/index.md","name":"GSD-2022-1000562","record":{"aliases":[],"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":"unknown","summary":"A memory leak in the Linux kernel vmbus driver could allow an attacker to cause a denial of service.","user_interaction":"unknown","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Drivers: hv: vmbus: Fix memory leak in vmbus_add_channel_kobj\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.16.11 by commit 92e25b637cd4e010f776c86e4810300e773eac5c, it was introduced in version v4.15 by commit c2e5df616e1ae6c2a074cb241ebb65a318ebaf7c. For more details please see the references link.","ecosystems":["Linux"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Drivers: hv: vmbus: Fix memory leak in vmbus_add_channel_kobj","id":"GSD-2022-1000562","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Linux","product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Linux","fixed":[],"introduced":[],"last_affected":[],"package":"Kernel","purl":null,"source":"GSD-2022-1000562"}],"products":null,"published":"2022-02-27","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"Global Security Database","prefix":"GSD"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A memory leak in the Linux kernel vmbus driver could allow an attacker to cause a denial of service.","url":"https://insights.sbomify.com/GSD-2022-1000562/"}