Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b88baab828713ce0b49b185444b2ee83bed373a8 – < a129b2b875c148aba233ace8447a0c36ca3bae07
    • affected b88baab828713ce0b49b185444b2ee83bed373a8 – < 196ce9e5e93202da097062be24e404984dbc5ac2
    • affected b88baab828713ce0b49b185444b2ee83bed373a8 – < 1101cbfe7f342e5eaaf7444965d4f1215abdac4c
    • affected b88baab828713ce0b49b185444b2ee83bed373a8 – < c60033c172420179b7bbb3d1f843f8dc90164dc5
    • affected b88baab828713ce0b49b185444b2ee83bed373a8 – < 38a62306c4266bcb3cd89e33c7111ee33096ebb3
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89800 badge
[![CVE-2026-89800](https://cveledger.app/badge/CVE-2026-89800.svg)](https://cveledger.app/cve/CVE-2026-89800)

Record last updated .