CVE-2025-71130 (GCVE-0-2025-71130)
Vulnerability from cvelistv5 – Published: 2026-01-14 15:07 – Updated: 2026-01-14 15:07
VLAI?
Title
drm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer
Initialize the eb.vma array with values of 0 when the eb structure is
first set up. In particular, this sets the eb->vma[i].vma pointers to
NULL, simplifying cleanup and getting rid of the bug described below.
During the execution of eb_lookup_vmas(), the eb->vma array is
successively filled up with struct eb_vma objects. This process includes
calling eb_add_vma(), which might fail; however, even in the event of
failure, eb->vma[i].vma is set for the currently processed buffer.
If eb_add_vma() fails, eb_lookup_vmas() returns with an error, which
prompts a call to eb_release_vmas() to clean up the mess. Since
eb_lookup_vmas() might fail during processing any (possibly not first)
buffer, eb_release_vmas() checks whether a buffer's vma is NULL to know
at what point did the lookup function fail.
In eb_lookup_vmas(), eb->vma[i].vma is set to NULL if either the helper
function eb_lookup_vma() or eb_validate_vma() fails. eb->vma[i+1].vma is
set to NULL in case i915_gem_object_userptr_submit_init() fails; the
current one needs to be cleaned up by eb_release_vmas() at this point,
so the next one is set. If eb_add_vma() fails, neither the current nor
the next vma is set to NULL, which is a source of a NULL deref bug
described in the issue linked in the Closes tag.
When entering eb_lookup_vmas(), the vma pointers are set to the slab
poison value, instead of NULL. This doesn't matter for the actual
lookup, since it gets overwritten anyway, however the eb_release_vmas()
function only recognizes NULL as the stopping value, hence the pointers
are being set to NULL as they go in case of intermediate failure. This
patch changes the approach to filling them all with NULL at the start
instead, rather than handling that manually during failure.
(cherry picked from commit 08889b706d4f0b8d2352b7ca29c2d8df4d0787cd)
Severity ?
No CVSS data available.
Assigner
References
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Linux | Linux |
Affected:
544460c33821b44c2f0c643121303c3dc3f66ef1 , < 25d69e07770745992387c016613fd7ac8eaf9893
(git)
Affected: 544460c33821b44c2f0c643121303c3dc3f66ef1 , < 0336188cc85d0eab8463bd1bbd4ded4e9602de8b (git) Affected: 544460c33821b44c2f0c643121303c3dc3f66ef1 , < 24d55ac8e31d2f8197bfad71ffcb3bae21ed7117 (git) Affected: 544460c33821b44c2f0c643121303c3dc3f66ef1 , < 63f23aa2fbb823c8b15a29269fde220d227ce5b3 (git) Affected: 544460c33821b44c2f0c643121303c3dc3f66ef1 , < 4fe2bd195435e71c117983d87f278112c5ab364c (git) |
||
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "25d69e07770745992387c016613fd7ac8eaf9893",
"status": "affected",
"version": "544460c33821b44c2f0c643121303c3dc3f66ef1",
"versionType": "git"
},
{
"lessThan": "0336188cc85d0eab8463bd1bbd4ded4e9602de8b",
"status": "affected",
"version": "544460c33821b44c2f0c643121303c3dc3f66ef1",
"versionType": "git"
},
{
"lessThan": "24d55ac8e31d2f8197bfad71ffcb3bae21ed7117",
"status": "affected",
"version": "544460c33821b44c2f0c643121303c3dc3f66ef1",
"versionType": "git"
},
{
"lessThan": "63f23aa2fbb823c8b15a29269fde220d227ce5b3",
"status": "affected",
"version": "544460c33821b44c2f0c643121303c3dc3f66ef1",
"versionType": "git"
},
{
"lessThan": "4fe2bd195435e71c117983d87f278112c5ab364c",
"status": "affected",
"version": "544460c33821b44c2f0c643121303c3dc3f66ef1",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.16"
},
{
"lessThan": "5.16",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.160",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.120",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.19-rc4",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.160",
"versionStartIncluding": "5.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.120",
"versionStartIncluding": "5.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.64",
"versionStartIncluding": "5.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.4",
"versionStartIncluding": "5.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19-rc4",
"versionStartIncluding": "5.16",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer\n\nInitialize the eb.vma array with values of 0 when the eb structure is\nfirst set up. In particular, this sets the eb-\u003evma[i].vma pointers to\nNULL, simplifying cleanup and getting rid of the bug described below.\n\nDuring the execution of eb_lookup_vmas(), the eb-\u003evma array is\nsuccessively filled up with struct eb_vma objects. This process includes\ncalling eb_add_vma(), which might fail; however, even in the event of\nfailure, eb-\u003evma[i].vma is set for the currently processed buffer.\n\nIf eb_add_vma() fails, eb_lookup_vmas() returns with an error, which\nprompts a call to eb_release_vmas() to clean up the mess. Since\neb_lookup_vmas() might fail during processing any (possibly not first)\nbuffer, eb_release_vmas() checks whether a buffer\u0027s vma is NULL to know\nat what point did the lookup function fail.\n\nIn eb_lookup_vmas(), eb-\u003evma[i].vma is set to NULL if either the helper\nfunction eb_lookup_vma() or eb_validate_vma() fails. eb-\u003evma[i+1].vma is\nset to NULL in case i915_gem_object_userptr_submit_init() fails; the\ncurrent one needs to be cleaned up by eb_release_vmas() at this point,\nso the next one is set. If eb_add_vma() fails, neither the current nor\nthe next vma is set to NULL, which is a source of a NULL deref bug\ndescribed in the issue linked in the Closes tag.\n\nWhen entering eb_lookup_vmas(), the vma pointers are set to the slab\npoison value, instead of NULL. This doesn\u0027t matter for the actual\nlookup, since it gets overwritten anyway, however the eb_release_vmas()\nfunction only recognizes NULL as the stopping value, hence the pointers\nare being set to NULL as they go in case of intermediate failure. This\npatch changes the approach to filling them all with NULL at the start\ninstead, rather than handling that manually during failure.\n\n(cherry picked from commit 08889b706d4f0b8d2352b7ca29c2d8df4d0787cd)"
}
],
"providerMetadata": {
"dateUpdated": "2026-01-14T15:07:46.508Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/25d69e07770745992387c016613fd7ac8eaf9893"
},
{
"url": "https://git.kernel.org/stable/c/0336188cc85d0eab8463bd1bbd4ded4e9602de8b"
},
{
"url": "https://git.kernel.org/stable/c/24d55ac8e31d2f8197bfad71ffcb3bae21ed7117"
},
{
"url": "https://git.kernel.org/stable/c/63f23aa2fbb823c8b15a29269fde220d227ce5b3"
},
{
"url": "https://git.kernel.org/stable/c/4fe2bd195435e71c117983d87f278112c5ab364c"
}
],
"title": "drm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2025-71130",
"datePublished": "2026-01-14T15:07:46.508Z",
"dateReserved": "2026-01-13T15:30:19.655Z",
"dateUpdated": "2026-01-14T15:07:46.508Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2025-71130\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-01-14T15:16:02.747\",\"lastModified\":\"2026-01-14T16:25:12.057\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer\\n\\nInitialize the eb.vma array with values of 0 when the eb structure is\\nfirst set up. In particular, this sets the eb-\u003evma[i].vma pointers to\\nNULL, simplifying cleanup and getting rid of the bug described below.\\n\\nDuring the execution of eb_lookup_vmas(), the eb-\u003evma array is\\nsuccessively filled up with struct eb_vma objects. This process includes\\ncalling eb_add_vma(), which might fail; however, even in the event of\\nfailure, eb-\u003evma[i].vma is set for the currently processed buffer.\\n\\nIf eb_add_vma() fails, eb_lookup_vmas() returns with an error, which\\nprompts a call to eb_release_vmas() to clean up the mess. Since\\neb_lookup_vmas() might fail during processing any (possibly not first)\\nbuffer, eb_release_vmas() checks whether a buffer\u0027s vma is NULL to know\\nat what point did the lookup function fail.\\n\\nIn eb_lookup_vmas(), eb-\u003evma[i].vma is set to NULL if either the helper\\nfunction eb_lookup_vma() or eb_validate_vma() fails. eb-\u003evma[i+1].vma is\\nset to NULL in case i915_gem_object_userptr_submit_init() fails; the\\ncurrent one needs to be cleaned up by eb_release_vmas() at this point,\\nso the next one is set. If eb_add_vma() fails, neither the current nor\\nthe next vma is set to NULL, which is a source of a NULL deref bug\\ndescribed in the issue linked in the Closes tag.\\n\\nWhen entering eb_lookup_vmas(), the vma pointers are set to the slab\\npoison value, instead of NULL. This doesn\u0027t matter for the actual\\nlookup, since it gets overwritten anyway, however the eb_release_vmas()\\nfunction only recognizes NULL as the stopping value, hence the pointers\\nare being set to NULL as they go in case of intermediate failure. This\\npatch changes the approach to filling them all with NULL at the start\\ninstead, rather than handling that manually during failure.\\n\\n(cherry picked from commit 08889b706d4f0b8d2352b7ca29c2d8df4d0787cd)\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0336188cc85d0eab8463bd1bbd4ded4e9602de8b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/24d55ac8e31d2f8197bfad71ffcb3bae21ed7117\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/25d69e07770745992387c016613fd7ac8eaf9893\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/4fe2bd195435e71c117983d87f278112c5ab364c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/63f23aa2fbb823c8b15a29269fde220d227ce5b3\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…