{"answers":{"affected":"1 open source package ship an affected version, including Kernel.","exploited":"There is no known exploitation of GSD-2022-1003313 in the wild and no public exploit code.","fix":"No fix has been published for GSD-2022-1003313 yet. Limit exposure of the affected software until one is available.","what":"GSD-2022-1003313 is a 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-1003313 and fix it if it is affected.\n\nWhat it is: GSD-2022-1003313 is a 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-1003313 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-1003313/ (Markdown: https://insights.sbomify.com/GSD-2022-1003313/index.md)","id":"GSD-2022-1003313","markdown":"https://insights.sbomify.com/GSD-2022-1003313/index.md","name":"GSD-2022-1003313","record":{"aliases":[],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux Kernel","requires_auth":"none","summary":"A bug in the Linux Kernel BFQ scheduler fails to update cgroup information before merging bio, potentially causing incorrect resource accounting.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"bfq: Update cgroup information before merging bio\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.15.46 by commit e8821f45612f2e6d9adb9c6ba0fb4184f57692aa, it was introduced in version v4.12 by commit e21b7a0b988772e82e7147e1c659a5afe2ae003c. 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":"bfq: Update cgroup information before merging bio","id":"GSD-2022-1003313","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Linux","product":null,"products":[],"type":"other","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Linux","fixed":[],"introduced":[],"last_affected":[],"package":"Kernel","purl":null,"source":"GSD-2022-1003313"}],"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 bug in the Linux Kernel BFQ scheduler fails to update cgroup information before merging bio, potentially causing incorrect resource accounting.","url":"https://insights.sbomify.com/GSD-2022-1003313/"}