{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98627 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98627 is a memory corruption 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-98627 and fix it if it is affected.\n\nWhat it is: CVE-2026-98627 is a memory corruption 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-98627 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-98627/ (Markdown: https://insights.sbomify.com/CVE-2026-98627/index.md)","id":"CVE-2026-98627","markdown":"https://insights.sbomify.com/CVE-2026-98627/index.md","name":"CVE-2026-98627","record":{"aliases":["DEBIAN-CVE-2026-98627","GHSA-p3gw-45vq-6cwq","UBUNTU-CVE-2026-98627"],"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 flaw in the Linux kernel BPF verifier allows out-of-bounds packet access, potentially leading to memory corruption and privilege escalation for local attackers.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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: Preserve packet pointer class displacement in regsafe()\n\nregsafe() maps packet pointer IDs between states and checks that each\ncurrent register range is a subset of the corresponding explored\nregister range. It does not, however, preserve the displacement between\nregisters that share a packet pointer ID.\n\nThis is unsound because packet range is shared by ID. A bounds check on\none class member updates every member, and a later access can consume the\nrange through another member. Commit 022ac0750883 (\"bpf: use reg-\u003evar_off\ninstead of reg-\u003eoff for pointers\") folded the fixed pointer offset into\nr64 and removed the old off equality check, so two individually narrower\nregisters can prune even when their displacement has changed. The\nexplored path can then license an out-of-bounds packet access on the\npruned path.\n\nRequire matching range bases for packet pointers with an ID. Together\nwith the existing ID mapping, this preserves the displacement between\nmembers of each packet-pointer class without adding per-ID state.\nPacket pointers without an ID remain unaffected.","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: Preserve packet pointer class displacement in regsafe()","id":"CVE-2026-98627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"bpf: Make post-verification instruction rewrites killable","id":"CVE-2026-98628"},"packages":[],"prev":{"headline":"bpf: Restrict CO-RE poisoning to relocatable instructions","id":"CVE-2026-98626"},"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 flaw in the Linux kernel BPF verifier allows out-of-bounds packet access, potentially leading to memory corruption and privilege escalation for local attackers.","url":"https://insights.sbomify.com/CVE-2026-98627/"}