VulnerabilityPublished 16 Sep 2026Updated 5 Oct 2026

CVE-2026-89800: Linux kernel · drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE

Affects Linux kernelSource GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected 6.17.0-5.5 – 7.0.0-38.38 23 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected 6.17.0-1003.3 – 7.0.0-1017.17 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected 7.0.0-1003.3 – 7.0.0-1016.16 9 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 13 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected 7.0.0-1002.3 – 7.0.0-1008.9 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix has been implemented to clear the dirty flag when unwinding the OP_UNMAP_SPARSE operation. Users should apply the official Linux kernel updates that include this patch for the affected versions to resolve the issue.

Description

A vulnerability in the Linux kernel's drm/nouveau/uvmm component was resolved by ensuring the dirty flag is cleared when unwinding an OP_UNMAP_SPARSE operation. Previously, if a later operation in the job failed, the dirty flag was never cleared, leaving the region marked dirty and causing subsequent bind operations over that range to fail permanently. This could result in errors such as -ENOENT, -EINVAL, or unkillable waits during bind validation.

Impact

Affected systems may experience permanent failures in memory binding operations within the drm/nouveau/uvmm subsystem, leading to errors such as -ENOENT, -EINVAL, or indefinite waits in bind validation. This can degrade system stability or functionality related to GPU memory management but does not indicate direct privilege escalation or code execution.

Summary

The Linux kernel's drm/nouveau/uvmm subsystem had a flaw where the dirty flag on a region was set during an OP_UNMAP_SPARSE operation but not cleared if the operation was unwound due to a failure in a later operation. This left the region in an inconsistent state with the dirty flag set and the region still present in the uvmm region tree, causing permanent failures in subsequent bind operations over the affected memory range. The fix clears the dirty flag during the unwind process, restoring the region to its original state and preventing permanent bind failures.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2026, 19:15 UTC

Technical details

References

Community reviews

Related threats