CVE-2026-98641
Received Received - Intake

BPF Exception Callback Frame Pointer Misconfiguration

Vulnerability report for CVE-2026-98641, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-18

Last updated on: 2026-10-18

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: set up the frame pointer for the exception callback A program acting as exception boundary saves all callee-saved registers, so build_prologue() takes the exception_cb path and never calls push_callee_regs(). That is the only place find_used_callee_regs() runs, and with it the only place ctx->fp_used is set, so the callback prologue does not emit the mov x25, sp that points BPF_REG_FP at the frame the callback runs on. x25 keeps whatever it held when bpf_throw() was called. If the throw came from a subprogram that uses its own BPF stack, that is the subprogram's frame pointer, and since the subprogram never returns it never restores x25 either. Stack accesses through BPF_REG_FP are rewritten to be stack pointer relative, so those still land in the callback's own frame. Materializing the register does not: a callback that passes the address of a local variable to a helper hands over an address in the dead subprogram's frame. That address is below the callback's stack pointer by then, and the helper's own call chain covers it, so the helper can write over its own return address. 0x1234 below is the value the helper was asked to store: pc : 0x1234 lr : 0x1234 Call trace: 0x1234 (P) bpf_test_run+0x188/0x3e0 bpf_prog_test_run_skb+0x47c/0x998 __sys_bpf+0xbdc/0xdd8 Kernel panic - not syncing: Oops: Fatal exception in interrupt Set ctx->fp_used on the exception callback path so that the existing code further down sets x25 from the stack pointer. The epilogue restores it from the main program's save area along with the other callee-saved registers, as it already does. x86 sets the frame pointer for the callback from the argument it is passed, and powerpc computes it from the stack pointer.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-18
Last Modified
2026-10-18
Generated
2026-10-18
AI Q&A
2026-10-18
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
Linux Linux 5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff
Linux Linux 5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff
Linux Linux 5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff
Linux Linux 5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff
Linux Linux 6.12

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Linux kernel vulnerability in the BPF (Berkeley Packet Filter) subsystem for arm64 systems. It involves incorrect frame pointer setup during exception handling in BPF programs. When an exception occurs, the kernel fails to properly set the frame pointer register (x25) for the callback prologue, leading to potential stack corruption. This happens because the exception callback path bypasses the normal register saving process, causing the frame pointer to retain a stale value from a previous subprogram's stack frame.

Impact Analysis

This vulnerability could allow an attacker with local access to trigger a kernel panic or execute arbitrary code in the kernel context. Successful exploitation might lead to system crashes, privilege escalation, or bypass of security mechanisms. The impact is limited to systems running vulnerable Linux kernels with BPF enabled, particularly on arm64 architectures.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-98641. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart