{"answers":{"affected":"1 open source package ship an affected version, including Kernel.","exploited":"There is no known exploitation of GSD-2022-1005166 in the wild and no public exploit code.","fix":"No fix has been published for GSD-2022-1005166 yet. Limit exposure of the affected software until one is available.","what":"GSD-2022-1005166 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-1005166 and fix it if it is affected.\n\nWhat it is: GSD-2022-1005166 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-1005166 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-1005166/ (Markdown: https://insights.sbomify.com/GSD-2022-1005166/index.md)","id":"GSD-2022-1005166","markdown":"https://insights.sbomify.com/GSD-2022-1005166/index.md","name":"GSD-2022-1005166","record":{"aliases":[],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel tracing","requires_auth":"high_privilege","summary":"Restricts eprobes from using stack or register variables to prevent potential security issues in Linux kernel tracing.","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":"tracing/eprobes: Do not allow eprobes to use $stack, or % for regs\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.4 by commit 7c262114a576d94c0ced80e232bbb17391a55908, it was introduced in version v5.15 by commit 7491e2c442781a1860181adb5ab472a52075f393. 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":"tracing/eprobes: Do not allow eprobes to use $stack, or % for regs","id":"GSD-2022-1005166","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-1005166"}],"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":"Restricts eprobes from using stack or register variables to prevent potential security issues in Linux kernel tracing.","url":"https://insights.sbomify.com/GSD-2022-1005166/"}