CVE-2026-89800

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

N/A
Published: September 16, 2026 at 10:30 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.6b88baab828713ce0b49b185444b2ee83bed373a8
Vendor states this is fixed in 1101cbfe7f342e5eaaf7444965d4f1215abdac4c (fixed)
Vendor states this is fixed in 196ce9e5e93202da097062be24e404984dbc5ac2 (fixed)
Vendor states this is fixed in 38a62306c4266bcb3cd89e33c7111ee33096ebb3 (fixed)
Vendor states this is fixed in a129b2b875c148aba233ace8447a0c36ca3bae07 (fixed)
Vendor states this is fixed in c60033c172420179b7bbb3d1f843f8dc90164dc5 (fixed)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card