{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98626 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98626 is a code injection vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98626 and fix it if it is affected.\n\nWhat it is: CVE-2026-98626 is a code injection vulnerability in Linux, published on 18 Oct 2026. 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 CVE-2026-98626 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/CVE-2026-98626/ (Markdown: https://insights.sbomify.com/CVE-2026-98626/index.md)","id":"CVE-2026-98626","markdown":"https://insights.sbomify.com/CVE-2026-98626/index.md","name":"CVE-2026-98626","record":{"aliases":["AZL-108947","BELL-CVE-2026-98626","DEBIAN-CVE-2026-98626","GHSA-7qcx-cmxq-wh7w","UBUNTU-CVE-2026-98626"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can exploit improper CO-RE relocation handling in the Linux kernel to inject malicious code or escalate privileges.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Restrict CO-RE poisoning to relocatable instructions\n\nCO-RE relocation records can name any instruction offset. When a\nrelocation cannot be resolved, bpf_core_patch_insn() currently poisons its\ntarget before checking whether that instruction is a valid relocation\ntarget. Malformed metadata can therefore replace jumps, calls, exits,\nregister-source arithmetic, or non-immediate loads instead of failing at\nthe relocation step.\n\nHandle poisoning only after the instruction has passed the same class and\noperand-form checks used for a resolved relocation. Route invalid forms\nthrough the existing diagnostic and return a hard error. Keep poisoning\nsupported instructions, including both halves of a plain ldimm64, so an\nunresolved relocation in dead code remains valid.\n\nExtend bpf_core_poison_insn() to poison both halves of ldimm64, and return\nits status directly from each validated instruction case. This avoids\nrouting the success path through a common label and leaves the helper free\nto report errors.\n\nThe shared relocation code applies this restriction to both libbpf and\nin-kernel CO-RE.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"bpf: Restrict CO-RE poisoning to relocatable instructions","id":"CVE-2026-98626","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"bpf: Preserve packet pointer class displacement in regsafe()","id":"CVE-2026-98627"},"packages":[],"prev":{"headline":"netfilter: flowtable: publish HW_DEAD after worker is done","id":"CVE-2026-98625"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can exploit improper CO-RE relocation handling in the Linux kernel to inject malicious code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-98626/"}