{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98589 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98589 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-98589 and fix it if it is affected.\n\nWhat it is: CVE-2026-98589 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-98589 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-98589/ (Markdown: https://insights.sbomify.com/CVE-2026-98589/index.md)","id":"CVE-2026-98589","markdown":"https://insights.sbomify.com/CVE-2026-98589/index.md","name":"CVE-2026-98589","record":{"aliases":["AZL-109116","BELL-CVE-2026-98589","DEBIAN-CVE-2026-98589","GHSA-2cxv-r576-wfcv","UBUNTU-CVE-2026-98589"],"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 Linux kernel BPF verifier flaw allows memory corruption via packet pointers in mutating subprograms, enabling local privilege escalation.","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 pkt arguments in mutating subprogs\n\nThe verifier tracks changes in how PTR_TO_PACKET registers'\nbounds are modified across subprog boundaries. PTR_TO_PACKET\nregisters are actually passed as PTR_TO_MEM, which is assumed\nvalid for the entire call. This is not the case with packet memory,\nwhere a pskb_* call may invalidate its memory region.\n\nReject BPF code that passes PTR_TO_PACKET pointers to subprogs that\nmay mutate a packet. We cannot pass the pointer as a true PTR_TO_PACKET\nbecause we would also need to somehow pass the PTR_TO_PACKET_META\nor PTR_TO_PACKET_END to the subprog. Since we cannot avoid representing\nthe pointer in the subprog as PTR_TO_MEM, only permit it if the\nsubprog is guaranteed not to mutate the packet.","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 pkt arguments in mutating subprogs","id":"CVE-2026-98589","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: Fix bpf_sock context code generation","id":"CVE-2026-98590"},"packages":[],"prev":{"headline":"bpf, sockmap: Reject max_entries \u003e INT_MAX in sock_map_alloc","id":"CVE-2026-98588"},"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 Linux kernel BPF verifier flaw allows memory corruption via packet pointers in mutating subprograms, enabling local privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-98589/"}