# CVE-2026-92519: riscv, bpf: Fix memory leak in bpf_jit_free

> A memory leak in the Linux kernel's RISC-V BPF JIT compiler allows local attackers to exhaust system memory, potentially causing denial of service.

- **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:** 21 Oct 2026
- **Also known as:** AZL-102816, BELL-CVE-2026-92519, DEBIAN-CVE-2026-92519, GHSA-94hw-5j8j-hwq4, UBUNTU-CVE-2026-92519

## What is CVE-2026-92519?

CVE-2026-92519 is a memory corruption 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:

riscv, bpf: Fix memory leak in bpf_jit_free

When bpf_int_jit_compile() is called for subprograms, it returns early
during the first pass (!prog->is_func || extra_pass is false), keeping
ctx->offset alive for the subsequent extra pass.

If JIT compilation fails for a later subprogram, the BPF core aborts
and calls bpf_jit_free() to clean up the first subprogram. However,
bpf_jit_free() fails to free jit_data->ctx.offset, which causes a
memory leak of the JIT context offsets array.

Fix this by adding the missing kfree(jit_data->ctx.offset) in
bpf_jit_free().

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


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

Apply the vendor's patch.

## Is CVE-2026-92519 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92519 is a memory corruption 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-92519 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-92519/ (Markdown: https://insights.sbomify.com/CVE-2026-92519/index.md)
```

## Sources

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

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