{"answers":{"affected":"1 open source package ship an affected version, including Kernel.","exploited":"There is no known exploitation of GSD-2022-1002856 in the wild and no public exploit code.","fix":"No fix has been published for GSD-2022-1002856 yet. Limit exposure of the affected software until one is available.","what":"GSD-2022-1002856 is a denial of service vulnerability in Kernel, published on 28 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GSD-2022-1002856 and fix it if it is affected.\n\nWhat it is: GSD-2022-1002856 is a denial of service vulnerability in Kernel, published on 28 Jun 2022. 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 GSD-2022-1002856 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-1002856/ (Markdown: https://insights.sbomify.com/GSD-2022-1002856/index.md)","id":"GSD-2022-1002856","markdown":"https://insights.sbomify.com/GSD-2022-1002856/index.md","name":"GSD-2022-1002856","record":{"aliases":[],"analysis":{"component_type":"kernel","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel filesystem","requires_auth":"none","summary":"A deadlock in the btrfs filesystem can cause a denial of service when concurrent direct I/O writes occur under low free space conditions.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"btrfs: fix deadlock between concurrent dio writes when low on free data space\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.18.3 by commit cfae6f765b3c40882ee90dae8fbf9325c8de9c35, it was introduced in version v5.17 by commit f0bfa76a11e93d0fe2c896fcb566568c5e8b5d3f. 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":"btrfs: fix deadlock between concurrent dio writes when low on free data space","id":"GSD-2022-1002856","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Linux","product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Linux","fixed":[],"introduced":[],"last_affected":[],"package":"Kernel","purl":null,"source":"GSD-2022-1002856"}],"products":null,"published":"2022-06-28","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 deadlock in the btrfs filesystem can cause a denial of service when concurrent direct I/O writes occur under low free space conditions.","url":"https://insights.sbomify.com/GSD-2022-1002856/"}