CVE-2026-68271
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.
Affected versions
Linux kernel versions
6.6
and later are affected. Fixed in
6.6.148,
6.12.101,
6.18.42,
7.1.6,
7.2
and their respective stable series.
References
5 totalFrequently asked questions
-
What is CVE-2026-68271?
CVE-2026-68271 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.6 onward and has been patched in 6.6.148, 6.12.101, 6.18.42 and others. CVE-2026-68271 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-68271?
Yes. CVE-2026-68271 has been patched. Fixed versions include 6.6.148, 6.12.101, 6.18.42 and others. If you are running Linux kernel 6.6 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-68271 actively exploited?
No. CVE-2026-68271 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.