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-68271drm/nouveau: fix reversed error cleanup order in ucopy functions

Description

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix reversed error cleanup order in ucopy functions nouveau_uvmm_vm_bind_ucopy() and nouveau_exec_ucopy() place their error cleanup labels in allocation order rather than reverse allocation order. On a u_memcpya() failure for in_sync.s, the goto to err_free_ops (or err_free_pushs) frees the first allocation and then falls through to err_free_ins, which calls u_free() on args->in_sync.s. Since args->in_sync.s still holds the ERR_PTR returned by the failed u_memcpya(), and ERR_PTR values are not caught by ZERO_OR_NULL_PTR(), kvfree() proceeds to dereference it, which can result in a kernel oops. A failure for out_sync.s instead jumps to err_free_ins and skips freeing the first allocation, leading to a memory leak. Fix by swapping the cleanup label order so resources are freed in the correct reverse allocation sequence.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 7 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.18% · top 93% of all CVEs (12 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 – < 2473ac314387a5def7244eb6d6a345934ed140bf
    • affected b88baab828713ce0b49b185444b2ee83bed373a8 – < e15c25c7972d38a9f6bf8c3f7f29179a67263eba
    • affected b88baab828713ce0b49b185444b2ee83bed373a8 – < 4e109faa9ea2b6c04cc5a99e76db3126575a59d1
    • affected b88baab828713ce0b49b185444b2ee83bed373a8 – < ebbaf64d2635d1e78196c067fa8fa582a7dc17f7
    • affected b88baab828713ce0b49b185444b2ee83bed373a8 – < ab99ead646b1b833ecd57fe577a2816f2e848167
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .