{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98599 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98599 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-98599 and fix it if it is affected.\n\nWhat it is: CVE-2026-98599 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-98599 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-98599/ (Markdown: https://insights.sbomify.com/CVE-2026-98599/index.md)","id":"CVE-2026-98599","markdown":"https://insights.sbomify.com/CVE-2026-98599/index.md","name":"CVE-2026-98599","record":{"aliases":["AZL-109412","BELL-CVE-2026-98599","DEBIAN-CVE-2026-98599","GHSA-6688-ppfm-xwh9","UBUNTU-CVE-2026-98599"],"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 BPF","requires_auth":"low_privilege","summary":"A flaw in the Linux kernel BPF subsystem allows attackers to corrupt memory and potentially execute code by exploiting incorrect stack slot offset validation.","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: Reject non-negative offsets in stack_slot_obj_get_spi()\n\nbpf_get_spi() computes (-off - 1) / BPF_REG_SIZE using C division,\nwhich truncates toward zero. For off == 0, this produces spi 0, the\nsame index used by the valid stack slot at fp-8.\n\nstack_slot_obj_get_spi() currently checks alignment and the resulting\nspi bounds, but does not reject the non-negative offset itself. It can\ntherefore validate a PTR_TO_STACK register holding fp+0 against an\niterator stored at fp-8 even though the runtime receives the actual fp+0\npointer. An effectful iterator kfunc can then interpret memory outside\nthe BPF stack as iterator state.\n\nReject non-negative offsets before converting the offset to an spi. All\nvalid stack objects begin at a negative offset from the frame pointer.","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: Reject non-negative offsets in stack_slot_obj_get_spi()","id":"CVE-2026-98599","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":"Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame()","id":"CVE-2026-98600"},"packages":[],"prev":{"headline":"ipv6: Prevent rt6_insert_exception() for dying fib6_info.","id":"CVE-2026-98598"},"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 subsystem allows attackers to corrupt memory and potentially execute code by exploiting incorrect stack slot offset validation.","url":"https://insights.sbomify.com/CVE-2026-98599/"}