From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68271: drm/nouveau: fix reversed error cleanup order in ucopy functions
Date: Mon, 10 Aug 2026 13:59:48 +0200 [thread overview]
Message-ID: <2026081024-CVE-2026-68271-5d19@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-68271 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6 with commit b88baab828713ce0b49b185444b2ee83bed373a8 and fixed in 6.6.148 with commit 2473ac314387a5def7244eb6d6a345934ed140bf
Issue introduced in 6.6 with commit b88baab828713ce0b49b185444b2ee83bed373a8 and fixed in 6.12.101 with commit e15c25c7972d38a9f6bf8c3f7f29179a67263eba
Issue introduced in 6.6 with commit b88baab828713ce0b49b185444b2ee83bed373a8 and fixed in 6.18.42 with commit 4e109faa9ea2b6c04cc5a99e76db3126575a59d1
Issue introduced in 6.6 with commit b88baab828713ce0b49b185444b2ee83bed373a8 and fixed in 7.1.6 with commit ebbaf64d2635d1e78196c067fa8fa582a7dc17f7
Issue introduced in 6.6 with commit b88baab828713ce0b49b185444b2ee83bed373a8 and fixed in 7.2-rc1 with commit ab99ead646b1b833ecd57fe577a2816f2e848167
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-68271
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/nouveau/nouveau_exec.c
drivers/gpu/drm/nouveau/nouveau_uvmm.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/2473ac314387a5def7244eb6d6a345934ed140bf
https://git.kernel.org/stable/c/e15c25c7972d38a9f6bf8c3f7f29179a67263eba
https://git.kernel.org/stable/c/4e109faa9ea2b6c04cc5a99e76db3126575a59d1
https://git.kernel.org/stable/c/ebbaf64d2635d1e78196c067fa8fa582a7dc17f7
https://git.kernel.org/stable/c/ab99ead646b1b833ecd57fe577a2816f2e848167
reply other threads:[~2026-08-10 12:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081024-CVE-2026-68271-5d19@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.