# CVE-2026-89802: drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op

> A local attacker with render-node access can trigger a kernel crash via a NULL pointer dereference in the nouveau driver during sparse map operations.

- **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:** 16 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-101243, BELL-CVE-2026-89802, DEBIAN-CVE-2026-89802, GHSA-c2hc-j8hj-4mw2, UBUNTU-CVE-2026-89802

## What is CVE-2026-89802?

CVE-2026-89802 is a vulnerability in Linux, published on 16 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:

drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op

Each bind_job_op is zeroed by kzalloc_obj() in bind_job_op_from_uop(),
and the OP_MAP_SPARSE case in nouveau_uvmm_bind_job_submit() only creates
a region, so op->ops stays NULL for a successfully processed sparse map.

If a later op in the same job fails, the reverse unwind loop revisits that
op and calls drm_gpuva_ops_free(&uvmm->base, op->ops) unconditionally.
drm_gpuva_ops_free() dereferences its argument right away
(list_for_each_entry_safe on &ops->list), so a NULL op->ops oopses. The
path is reachable by any render-node fd holder, since NOUVEAU_VM_BIND is
DRM_RENDER_ALLOW.

Guard the free with IS_ERR_OR_NULL(), as nouveau_uvmm_bind_job_cleanup()
already does for the identical free.

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


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

Apply the vendor's patch.

## Is CVE-2026-89802 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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