Skip to content
Heist/ feed
UnratedFix available

drm/nouveau: fix reversed error cleanup order in ucopy functions

Type: advisorySource: OSV1 source record

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.

Announced Source revision 1
Original source ↗

CVE-2026-68271

Primary source · Revision 1

Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.

Security context

Source reference: osv:CVE-2026-68271

Kernel

Source reference: /affected/1/package/name

Affected versions
Not stated in this record
Fixed versions
6.6.148

Source reference: /affected/1/ranges

6.12.101

Source reference: /affected/1/ranges

6.18.42

Source reference: /affected/1/ranges

7.1.6

Source reference: /affected/1/ranges

Prerequisites
Not stated in this record

Structured affected-version data

Original package identities and version rules from this source.

[
  {
    "ranges": [
      {
        "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
        "type": "GIT",
        "events": [
          {
            "introduced": "b88baab828713ce0b49b185444b2ee83bed373a8"
          },
          {
            "fixed": "2473ac314387a5def7244eb6d6a345934ed140bf"
          },
          {
            "fixed": "e15c25c7972d38a9f6bf8c3f7f29179a67263eba"
          },
          {
            "fixed": "4e109faa9ea2b6c04cc5a99e76db3126575a59d1"
          },
          {
            "fixed": "ebbaf64d2635d1e78196c067fa8fa582a7dc17f7"
          },
          {
            "fixed": "ab99ead646b1b833ecd57fe577a2816f2e848167"
          }
        ]
      }
    ],
    "database_specific": {
      "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68271.json"
    }
  },
  {
    "ranges": [
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.6.0"
          },
          {
            "fixed": "6.6.148"
          }
        ]
      },
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.7.0"
          },
          {
            "fixed": "6.12.101"
          }
        ]
      },
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.13.0"
          },
          {
            "fixed": "6.18.42"
          }
        ]
      },
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.19.0"
          },
          {
            "fixed": "7.1.6"
          }
        ]
      }
    ],
    "package": {
      "name": "Kernel",
      "ecosystem": "Linux"
    },
    "database_specific": {
      "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68271.json"
    }
  }
]
Related CVEs
CVE-2026-68271

Source reference: /id

Publisher severity

No explicit severity was provided.

Event
#50695 · Revision 1
Added to Heist Feed
Publisher date
Read the original announcement