CVE-2026-68271drm/nouveau: fix reversed error cleanup order in ucopy functions
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from b88baab828713ce0b49b185444b2ee83bed373a8 before 2473ac314387a5def7244eb6d6a345934ed140bf; from b88baab828713ce0b49b185444b2ee83bed373a8 before e15c25c7972d38a9f6bf8c3f7f29179a67263eba; from b88baab828713ce0b49b185444b2ee83bed373a8 before 4e109faa9ea2b6c04cc5a99e76db3126575a59d1; from b88baab828713ce0b49b185444b2ee83bed373a8 before ebbaf64d2635d1e78196c067fa8fa582a7dc17f7; from b88baab828713ce0b49b185444b2ee83bed373a8 before ab99ead646b1b833ecd57fe577a2816f2e848167 | CNA record |
References
- 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
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.