# CVE-2026-98572: bpf: Fix immediate JMP JEQ/JNE on MIPS32

> A bug in the Linux kernel's BPF JIT compiler for MIPS32 causes invalid comparisons, potentially leading to denial of service or incorrect program behavior.

- **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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-109202, BELL-CVE-2026-98572, DEBIAN-CVE-2026-98572, GHSA-jqhp-gcf3-75rx, UBUNTU-CVE-2026-98572

## What is CVE-2026-98572?

CVE-2026-98572 is a vulnerability in Linux, published on 18 Oct 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: Fix immediate JMP JEQ/JNE on MIPS32

An addu instruction was emitted instead of addiu, causing the immediate
value 1 to be interpreted as register $at. This made the comparison
result invalid when the immediate operand was negative. Note that $at
is mapped to BPF_REG_AX, which is used for constant blinding.

Fix the instruction to use the immediate form.

Found with test_bpf on MIPS32r1 emulated by QEMU.

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


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

Apply the vendor's patch.

## Is CVE-2026-98572 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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