{"answers":{"affected":"1 open source package ship an affected version, including Kernel.","exploited":"There is no known exploitation of GSD-2021-1000362 in the wild and no public exploit code.","fix":"No fix has been published for GSD-2021-1000362 yet. Limit exposure of the affected software until one is available.","what":"GSD-2021-1000362 is a memory corruption vulnerability in Kernel, published on 31 May 2021. 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-2021-1000362 and fix it if it is affected.\n\nWhat it is: GSD-2021-1000362 is a memory corruption vulnerability in Kernel, published on 31 May 2021. 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-2021-1000362 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-2021-1000362/ (Markdown: https://insights.sbomify.com/GSD-2021-1000362/index.md)","id":"GSD-2021-1000362","markdown":"https://insights.sbomify.com/GSD-2021-1000362/index.md","name":"GSD-2021-1000362","record":{"aliases":[],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A flaw in Linux kernel powerpc/64s radix page table updates allows local attackers to corrupt kernel memory, potentially leading to privilege escalation or code execution.","user_interaction":"not_required","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":"powerpc/64s: Fix pte update for kernel memory on radix\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.10.37 by commit 84c0762633f2a7ac8399e6b97d3b9bb8e6e1d50f, it was introduced in version v4.18 by commit f1cb8f9beba8699dd1b4518418191499e53f7b17. 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":"powerpc/64s: Fix pte update for kernel memory on radix","id":"GSD-2021-1000362","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Linux","product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Linux","fixed":[],"introduced":[],"last_affected":[],"package":"Kernel","purl":null,"source":"GSD-2021-1000362"}],"products":null,"published":"2021-05-31","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 flaw in Linux kernel powerpc/64s radix page table updates allows local attackers to corrupt kernel memory, potentially leading to privilege escalation or code execution.","url":"https://insights.sbomify.com/GSD-2021-1000362/"}