# CVE-2026-68295: LoongArch: BPF: Zero-extend signed ALU32 div/mod results

> A flaw in the LoongArch BPF JIT compiler mishandles signed division results, potentially allowing attackers to execute arbitrary code via crafted BPF programs.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 10 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-68295, DEBIAN-CVE-2026-68295, GHSA-vrqj-mf6p-p2fv, UBUNTU-CVE-2026-68295

## What is CVE-2026-68295?

CVE-2026-68295 is a high-severity vulnerability in Linux, published on 10 Aug 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:

LoongArch: BPF: Zero-extend signed ALU32 div/mod results

ALU32 operations write a 32-bit result and leave the upper 32 bits of
the BPF register zero. The LoongArch JIT sign-extends the result of
signed ALU32 BPF_DIV and BPF_MOD (off=1), so a negative 32-bit quotient
or remainder leaves bits 63:32 set in JITted code while the verifier
and interpreter model those bits as zero.

Keep sign-extension on the operands, which signed divide needs, and
zero-extend the ALU32 result after the divide or modulo instruction,
matching the unsigned ALU32 div/mod paths and every other ALU32
operation in this JIT.

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


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

Apply the vendor's patch.

## Is CVE-2026-68295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68295 is a high-severity vulnerability in Linux, published on 10 Aug 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-68295 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-68295/ (Markdown: https://insights.sbomify.com/CVE-2026-68295/index.md)
```

## Sources

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

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