{"answers":{"affected":"1 open source package ship an affected version, including Kernel.","exploited":"There is no known exploitation of GSD-2022-1005025 in the wild and no public exploit code.","fix":"No fix has been published for GSD-2022-1005025 yet. Limit exposure of the affected software until one is available.","what":"GSD-2022-1005025 is a vulnerability in Kernel, published on 16 Sep 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-1005025 and fix it if it is affected.\n\nWhat it is: GSD-2022-1005025 is a vulnerability in Kernel, published on 16 Sep 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-1005025 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-1005025/ (Markdown: https://insights.sbomify.com/GSD-2022-1005025/index.md)","id":"GSD-2022-1005025","markdown":"https://insights.sbomify.com/GSD-2022-1005025/index.md","name":"GSD-2022-1005025","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 shmem subsystem fails to update folio state after page replacement, potentially causing memory inconsistencies.","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":"shmem: update folio if shmem_replace_page() updates the page\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.19.6 by commit c061d697a304cc652a21eae4c252299de7e28cc5, it was introduced in version v5.19 by commit da08e9b7932345aff0a748c55f8a25709505f2a3. 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":"shmem: update folio if shmem_replace_page() updates the page","id":"GSD-2022-1005025","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-1005025"}],"products":null,"published":"2022-09-16","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 shmem subsystem fails to update folio state after page replacement, potentially causing memory inconsistencies.","url":"https://insights.sbomify.com/GSD-2022-1005025/"}