{"api_version":"1","generated_at":"2026-10-22T07:13:14+00:00","cve":"CVE-2026-98641","urls":{"html":"https://cve.report/CVE-2026-98641","api":"https://cve.report/api/cve/CVE-2026-98641.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98641","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98641"},"summary":{"title":"bpf, arm64: set up the frame pointer for the exception callback","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->fp_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->fp_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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-18 16:17:17","updated_at":"2026-10-19 10:19:28"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/ef1fb82f12186dd26153b14d9fbcf4ec98db81b3","name":"https://git.kernel.org/stable/c/ef1fb82f12186dd26153b14d9fbcf4ec98db81b3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/d7cd5ebe13989f265015910faa25e5d50faa4c22","name":"https://git.kernel.org/stable/c/d7cd5ebe13989f265015910faa25e5d50faa4c22","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ecdd770a9fc3eaf6c3127c5991312b84774a7b0f","name":"https://git.kernel.org/stable/c/ecdd770a9fc3eaf6c3127c5991312b84774a7b0f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b67b4c763f211e7a6391c356fef552e2ea63f08a","name":"https://git.kernel.org/stable/c/b67b4c763f211e7a6391c356fef552e2ea63f08a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98641","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98641","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff ecdd770a9fc3eaf6c3127c5991312b84774a7b0f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff b67b4c763f211e7a6391c356fef552e2ea63f08a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff d7cd5ebe13989f265015910faa25e5d50faa4c22 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff ef1fb82f12186dd26153b14d9fbcf4ec98db81b3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.12","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.112 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.55 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.9 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["arch/arm64/net/bpf_jit_comp.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"ecdd770a9fc3eaf6c3127c5991312b84774a7b0f","status":"affected","version":"5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff","versionType":"git"},{"lessThan":"b67b4c763f211e7a6391c356fef552e2ea63f08a","status":"affected","version":"5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff","versionType":"git"},{"lessThan":"d7cd5ebe13989f265015910faa25e5d50faa4c22","status":"affected","version":"5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff","versionType":"git"},{"lessThan":"ef1fb82f12186dd26153b14d9fbcf4ec98db81b3","status":"affected","version":"5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["arch/arm64/net/bpf_jit_comp.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.12"},{"lessThan":"6.12","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.112","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.55","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.9","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.112","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.55","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.9","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"6.12","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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->fp_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->fp_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."}],"providerMetadata":{"dateUpdated":"2026-10-19T09:23:10.965Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/ecdd770a9fc3eaf6c3127c5991312b84774a7b0f"},{"url":"https://git.kernel.org/stable/c/b67b4c763f211e7a6391c356fef552e2ea63f08a"},{"url":"https://git.kernel.org/stable/c/d7cd5ebe13989f265015910faa25e5d50faa4c22"},{"url":"https://git.kernel.org/stable/c/ef1fb82f12186dd26153b14d9fbcf4ec98db81b3"}],"title":"bpf, arm64: set up the frame pointer for the exception callback","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98641","datePublished":"2026-10-18T15:20:12.730Z","dateReserved":"2026-09-25T10:25:14.361Z","dateUpdated":"2026-10-19T09:23:10.965Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-18 16:17:17","lastModifiedDate":"2026-10-19 10:19:28","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98641","Ordinal":"1","Title":"bpf, arm64: set up the frame pointer for the exception callback","CVE":"CVE-2026-98641","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98641","Ordinal":"1","NoteData":"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->fp_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->fp_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.","Type":"Description","Title":"bpf, arm64: set up the frame pointer for the exception callback"}]}}}