CVE-2026-68271 (GCVE-0-2026-68271)
Vulnerability from cvelistv5
Published
2026-08-10 12:01
Modified
2026-08-17 05:02
Severity ?
VLAI Severity ?
EPSS score ?
Summary
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.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/nouveau/nouveau_exec.c",
"drivers/gpu/drm/nouveau/nouveau_uvmm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "2473ac314387a5def7244eb6d6a345934ed140bf",
"status": "affected",
"version": "b88baab828713ce0b49b185444b2ee83bed373a8",
"versionType": "git"
},
{
"lessThan": "e15c25c7972d38a9f6bf8c3f7f29179a67263eba",
"status": "affected",
"version": "b88baab828713ce0b49b185444b2ee83bed373a8",
"versionType": "git"
},
{
"lessThan": "4e109faa9ea2b6c04cc5a99e76db3126575a59d1",
"status": "affected",
"version": "b88baab828713ce0b49b185444b2ee83bed373a8",
"versionType": "git"
},
{
"lessThan": "ebbaf64d2635d1e78196c067fa8fa582a7dc17f7",
"status": "affected",
"version": "b88baab828713ce0b49b185444b2ee83bed373a8",
"versionType": "git"
},
{
"lessThan": "ab99ead646b1b833ecd57fe577a2816f2e848167",
"status": "affected",
"version": "b88baab828713ce0b49b185444b2ee83bed373a8",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/nouveau/nouveau_exec.c",
"drivers/gpu/drm/nouveau/nouveau_uvmm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.6"
},
{
"lessThan": "6.6",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.148",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.101",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.42",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.148",
"versionStartIncluding": "6.6",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.101",
"versionStartIncluding": "6.6",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.42",
"versionStartIncluding": "6.6",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.6",
"versionStartIncluding": "6.6",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "6.6",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/nouveau: fix reversed error cleanup order in ucopy functions\n\nnouveau_uvmm_vm_bind_ucopy() and nouveau_exec_ucopy() place their error\ncleanup labels in allocation order rather than reverse allocation order.\nOn a u_memcpya() failure for in_sync.s, the goto to err_free_ops (or\nerr_free_pushs) frees the first allocation and then falls through to\nerr_free_ins, which calls u_free() on args-\u003ein_sync.s.\n\nSince args-\u003ein_sync.s still holds the ERR_PTR returned by the failed\nu_memcpya(), and ERR_PTR values are not caught by ZERO_OR_NULL_PTR(),\nkvfree() proceeds to dereference it, which can result in a kernel oops.\nA failure for out_sync.s instead jumps to err_free_ins and skips freeing\nthe first allocation, leading to a memory leak.\n\nFix by swapping the cleanup label order so resources are freed in the\ncorrect reverse allocation sequence."
}
],
"providerMetadata": {
"dateUpdated": "2026-08-17T05:02:04.681Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/2473ac314387a5def7244eb6d6a345934ed140bf"
},
{
"url": "https://git.kernel.org/stable/c/e15c25c7972d38a9f6bf8c3f7f29179a67263eba"
},
{
"url": "https://git.kernel.org/stable/c/4e109faa9ea2b6c04cc5a99e76db3126575a59d1"
},
{
"url": "https://git.kernel.org/stable/c/ebbaf64d2635d1e78196c067fa8fa582a7dc17f7"
},
{
"url": "https://git.kernel.org/stable/c/ab99ead646b1b833ecd57fe577a2816f2e848167"
}
],
"title": "drm/nouveau: fix reversed error cleanup order in ucopy functions",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-68271",
"datePublished": "2026-08-10T12:01:46.534Z",
"dateReserved": "2026-07-30T09:28:09.378Z",
"dateUpdated": "2026-08-17T05:02:04.681Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…