CVE-2026-72359 (GCVE-0-2026-72359)
Vulnerability from cvelistv5
Published
2026-08-15 05:55
Modified
2026-08-17 05:13
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: fix NPD in bo_meminfo()
When a buffer object is purged, its ttm.resource is set to NULL via the
TTM pipeline gutting flow. However, the BO remains in the client's
object list until userspace explicitly closes the GEM handle. If memory
stats are queried during this time, accessing bo->ttm.resource->mem_type
will result in a NULL pointer dereference.
Fix this by safely skipping purged BOs in bo_meminfo, as they no longer
consume any memory.
User is getting NPD on device resume, and possible theory is that in
bo_move(), if we need to evict something to SYSTEM to save the CCS state,
but the BO is marked as dontneed, this won't trigger a move but will
nuke the pages, leaving us with a NULL bo resource. And the meminfo()
doesn't look ready to handle a NULL resource.
v2 (Sashiko):
- There could potentially be other cases where we might end up with a
NULL resource, so make this a general NULL check for now.
(cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/xe/xe_drm_client.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "5ff2212f0e0779b0b0cbf91fbf970144107c4257",
"status": "affected",
"version": "ad9843aac91a1eda12912a4922042ea04cfc29dc",
"versionType": "git"
},
{
"lessThan": "b5c55015d4164a0f206bcdcf2985da948b3c7837",
"status": "affected",
"version": "ad9843aac91a1eda12912a4922042ea04cfc29dc",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/xe/xe_drm_client.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.1"
},
{
"lessThan": "7.1",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.5",
"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": "7.1.5",
"versionStartIncluding": "7.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "7.1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe: fix NPD in bo_meminfo()\n\nWhen a buffer object is purged, its ttm.resource is set to NULL via the\nTTM pipeline gutting flow. However, the BO remains in the client\u0027s\nobject list until userspace explicitly closes the GEM handle. If memory\nstats are queried during this time, accessing bo-\u003ettm.resource-\u003emem_type\nwill result in a NULL pointer dereference.\n\nFix this by safely skipping purged BOs in bo_meminfo, as they no longer\nconsume any memory.\n\nUser is getting NPD on device resume, and possible theory is that in\nbo_move(), if we need to evict something to SYSTEM to save the CCS state,\nbut the BO is marked as dontneed, this won\u0027t trigger a move but will\nnuke the pages, leaving us with a NULL bo resource. And the meminfo()\ndoesn\u0027t look ready to handle a NULL resource.\n\nv2 (Sashiko):\n - There could potentially be other cases where we might end up with a\n NULL resource, so make this a general NULL check for now.\n\n(cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)"
}
],
"providerMetadata": {
"dateUpdated": "2026-08-17T05:13:09.946Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/5ff2212f0e0779b0b0cbf91fbf970144107c4257"
},
{
"url": "https://git.kernel.org/stable/c/b5c55015d4164a0f206bcdcf2985da948b3c7837"
}
],
"title": "drm/xe: fix NPD in bo_meminfo()",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-72359",
"datePublished": "2026-08-15T05:55:59.424Z",
"dateReserved": "2026-08-09T03:40:39.921Z",
"dateUpdated": "2026-08-17T05:13:09.946Z",
"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…