drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (CVE-2026-89800) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-89800

drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE

Answer in brief

CVE-2026-89800 records a Unknown severity vulnerability in drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 16, 2026Updated Sep 16, 2026Source checked Sep 16, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=b88baab828713ce0b49b185444b2ee83bed373a8 <a129b2b875c148aba233ace8447a0c36ca3bae07 \|\| >=b88baab828713ce0b49b185444b2ee83bed373a8 <196ce9e5e93202da097062be24e404984dbc5ac2 \|\| >=b88baab828713ce0b49b185444b2ee83bed373a8 <1101cbfe7f342e5eaaf7444965d4f1215abdac4c \|\| >=b88baab828713ce0b49b185444b2ee83bed373a8 <c60033c172420179b7bbb3d1f843f8dc90164dc5 \|\| >=b88baab828713ce0b49b185444b2ee83bed373a8 <38a62306c4266bcb3cd89e33c7111ee33096ebb3	a129b2b875c148aba233ace8447a0c36ca3bae07, 196ce9e5e93202da097062be24e404984dbc5ac2, 1101cbfe7f342e5eaaf7444965d4f1215abdac4c, c60033c172420179b7bbb3d1f843f8dc90164dc5, 38a62306c4266bcb3cd89e33c7111ee33096ebb3
Linux/Linuxgeneric	6.6	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to a129b2b875c148aba233ace8447a0c36ca3bae07 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 16, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE A successful OP_UNMAP_SPARSE marks its region dirty with nouveau_uvma_region_dirty() and defers the teardown to nouveau_uvmm_bind_job_cleanup(); it does not remove the region from uvmm->region_mt. If a later op in the job fails, the unwind path never clears reg->dirty (set in one place, cleared nowhere) and sets op->reg = NULL, so cleanup skips the teardown. The region is left in the tree with dirty set and its completion never signalled. Later binds over that range then fail permanently -- -ENOENT or -EINVAL from the dirty checks, or an unkillable wait_for_completion() in bind_validate_region() -- for the lifetime of the uvmm. Clear reg->dirty when the unwind reverts the sparse unmap, restoring the region to the state it was found in.

Quoted source text, attributed separately from HOL analysis.