CVE-2026-89801

HighCVSS 7.8

Published: 16/09/2026(UTC)Updated: 19/10/2026(UTC)Translated: 16/09/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.16%

5th percentile - higher than 5% of all known CVEs

Summary

In the Linux kernel, the drm/nouveau/uvmm driver had a premature region free on failed OP_UNMAP_SPARSE. Two failure paths left op->reg set, causing cleanup to remove and put a region the job never created, leading to a use-after-free. The fix clears op->reg on both failure paths.

Risk Assessment

A use-after-free can lead to kernel crash or potential privilege escalation. The vector is reachable by a render-node fd holder, increasing risk in multi-user environments.

Recommendation

Update the Linux kernel to a version with the drm/nouveau/uvmm fix. Restrict GPU device access for untrusted users.

Other vulnerabilities in Linux kernel (drm/nouveau/uvmm)

CVE-2026-89802Low risk· EPSS 9%
In the Linux kernel, the drm/nouveau/uvmm driver had a NULL dereference when unwinding an OP_MAP_SPARSE op. If a later op in the same job fails, the reverse unwind loop calls drm_gpuva_ops_free() on op->ops, which remains NULL for a successfully processed sparse map, causing an oops. The fix adds an IS_ERR_OR_NULL() guard.

Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE In nouveau_uvmm_bind_job_submit()'s OP_UNMAP_SPARSE arm, op->reg is set from nouveau_uvma_region_find(), which only looks the region up and takes no reference; a region's sole reference is its membership in uvmm->region_mt. Two failure paths leave op->reg set: the -ENOENT check when the region is busy, and the drm_gpuvm_sm_unmap_ops_create() failure. The sibling nouveau_uvmm_sm_unmap_prepare() failure just below clears op->reg; these two do not. unwind_continue steps back one op, so the failing op is skipped by the unwind loop and its op->reg stays set. nouveau_uvmm_bind_job_cleanup() then enters its if (op->reg) branch and calls nouveau_uvma_region_remove() and nouveau_uvma_region_put() on it, dropping the tree's sole reference and freeing a region this job never created. The comment above the cleanup loop documents the broken invariant: op->reg must be NULL on submit failure. This frees a live region on an unrelated failure, reachable single-job when drm_gpuvm_sm_unmap_ops_create() returns -ENOMEM; if another job owns the same region, its cleanup then removes and puts the freed region, a use-after-free. Clear op->reg on both failure paths.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS