{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98641 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98641 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-98641 and fix it if it is affected.\n\nWhat it is: CVE-2026-98641 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-98641 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-98641/ (Markdown: https://insights.sbomify.com/CVE-2026-98641/index.md)","id":"CVE-2026-98641","markdown":"https://insights.sbomify.com/CVE-2026-98641/index.md","name":"CVE-2026-98641","record":{"aliases":["BELL-CVE-2026-98641","DEBIAN-CVE-2026-98641","GHSA-rmw7-mmh2-5m8g","UBUNTU-CVE-2026-98641"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"no","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A flaw in the Linux kernel's BPF arm64 exception callback handling allows memory corruption, potentially leading to privilege escalation or code execution.","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, arm64: set up the frame pointer for the exception callback\n\nA program acting as exception boundary saves all callee-saved registers,\nso build_prologue() takes the exception_cb path and never calls\npush_callee_regs(). That is the only place find_used_callee_regs() runs,\nand with it the only place ctx-\u003efp_used is set, so the callback prologue\ndoes not emit the\n\n  mov x25, sp\n\nthat points BPF_REG_FP at the frame the callback runs on. x25 keeps\nwhatever it held when bpf_throw() was called. If the throw came from a\nsubprogram that uses its own BPF stack, that is the subprogram's frame\npointer, and since the subprogram never returns it never restores x25\neither.\n\nStack accesses through BPF_REG_FP are rewritten to be stack pointer\nrelative, so those still land in the callback's own frame. Materializing\nthe register does not: a callback that passes the address of a local\nvariable to a helper hands over an address in the dead subprogram's\nframe. That address is below the callback's stack pointer by then, and\nthe helper's own call chain covers it, so the helper can write over its\nown return address. 0x1234 below is the value the helper was asked to\nstore:\n\n  pc : 0x1234\n  lr : 0x1234\n  Call trace:\n   0x1234 (P)\n   bpf_test_run+0x188/0x3e0\n   bpf_prog_test_run_skb+0x47c/0x998\n   __sys_bpf+0xbdc/0xdd8\n  Kernel panic - not syncing: Oops: Fatal exception in interrupt\n\nSet ctx-\u003efp_used on the exception callback path so that the existing code\nfurther down sets x25 from the stack pointer. The epilogue restores it\nfrom the main program's save area along with the other callee-saved\nregisters, as it already does. x86 sets the frame pointer for the\ncallback from the argument it is passed, and powerpc computes it from\nthe stack 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, arm64: set up the frame pointer for the exception callback","id":"CVE-2026-98641","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"bpf: Fix UAF due to concurrent consumption of ttrace lists in alloc_bulk","id":"CVE-2026-98642"},"packages":[],"prev":{"headline":"HID: amd_sfh: Validate PCI BAR size before mapping","id":"CVE-2026-98640"},"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's BPF arm64 exception callback handling allows memory corruption, potentially leading to privilege escalation or code execution.","url":"https://insights.sbomify.com/CVE-2026-98641/"}