# CVE-2026-93044: bpf: Disallow interpreter fallback for arena-related insns

> A local attacker can trigger a kernel crash by loading BPF programs with arena instructions that force an unsupported interpreter fallback.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93044, DEBIAN-CVE-2026-93044, GHSA-pp7w-23pg-4fgh, UBUNTU-CVE-2026-93044

## What is CVE-2026-93044?

CVE-2026-93044 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

bpf: Disallow interpreter fallback for arena-related insns

Since the interpreter does not support the arena-related insns,
interpreter fallback should not be allowed for these insns in
core.c::__bpf_prog_select_runtime().

Currently, when the interpreter executes the arena ST/LDX/STX insns,
it would hit the BUG_ON() in ___bpf_prog_run() at run time.

[    2.579196] BPF interpreter: unknown opcode a2 (imm: 0x0)
[    2.579998] ------------[ cut here ]------------
[    2.580652] kernel BUG at kernel/bpf/core.c:2349!
[    2.581314] Oops: invalid opcode: 0000 [#1] SMP PTI

Set jit_required as true when arena map is used in the prog to disallow
interpreter fallback for arena-related insns.

## Which versions are affected by CVE-2026-93044?


## How do I fix CVE-2026-93044?

Apply the vendor's patch.

## Is CVE-2026-93044 being exploited?

There is no known exploitation of CVE-2026-93044 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93044 and fix it if it is affected.

What it is: CVE-2026-93044 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93044 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93044/ (Markdown: https://insights.sbomify.com/CVE-2026-93044/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93044
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93044
- OSV: https://osv.dev/vulnerability/CVE-2026-93044

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93044/
Summaries are generated and may contain mistakes; the official description above is the record.