GHSA-W7RF-7RXM-HR7V
Vulnerability from github – Published: 2026-08-10 15:33 – Updated: 2026-08-14 00:31In the Linux kernel, the following vulnerability has been resolved:
drm/xe/vm: Fix SVM leak on resv obj alloc failure in xe_vm_create()
Commit 9e9787414882 ("drm/xe/userptr: replace xe_hmm with gpusvm") made xe_svm_init() unconditional in xe_vm_create() and extended it to also initialize a "simple" gpusvm state for non-fault-mode VMs. The matching xe_svm_fini() call in xe_vm_close_and_put() was updated to run unconditionally, but the error unwind path in xe_vm_create() was not.
On the drm_gpuvm_resv_object_alloc() failure path, xe_svm_init() has already succeeded but xe_svm_fini() is only called when XE_VM_FLAG_FAULT_MODE is set. For non-fault-mode VMs this leaves vm->svm.gpusvm partially initialized and leaks the resources allocated by drm_gpusvm_init().
For fault-mode VMs, xe_svm_init() additionally acquires the pagemap owner via drm_pagemap_acquire_owner() and the pagemaps via xe_svm_get_pagemaps(). Those resources are released by xe_svm_close(), not xe_svm_fini(). On the same error path, xe_svm_close() is not called either, so fault-mode VMs leak the pagemap owner and pagemaps.
Fix both leaks:
-
Call xe_svm_fini() unconditionally on the err_svm_fini path, matching the unconditional xe_svm_init() call. Move the vm->size = 0 assignment out of the conditional so the xe_vm_is_closed() assert in xe_svm_fini() (and xe_svm_close()) holds for both modes.
-
Call xe_svm_close() for fault-mode VMs before xe_svm_fini(), matching the ordering used in xe_vm_close_and_put().
(cherry picked from commit ca2a3587d577ba764e0fe628fb676244fc33ddd4)
{
"affected": [],
"aliases": [
"CVE-2026-68298"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-10T13:20:19Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe/vm: Fix SVM leak on resv obj alloc failure in xe_vm_create()\n\nCommit 9e9787414882 (\"drm/xe/userptr: replace xe_hmm with gpusvm\") made\nxe_svm_init() unconditional in xe_vm_create() and extended it to also\ninitialize a \"simple\" gpusvm state for non-fault-mode VMs. The matching\nxe_svm_fini() call in xe_vm_close_and_put() was updated to run\nunconditionally, but the error unwind path in xe_vm_create() was not.\n\nOn the drm_gpuvm_resv_object_alloc() failure path, xe_svm_init() has\nalready succeeded but xe_svm_fini() is only called when\nXE_VM_FLAG_FAULT_MODE is set. For non-fault-mode VMs this leaves\nvm-\u003esvm.gpusvm partially initialized and leaks the resources allocated\nby drm_gpusvm_init().\n\nFor fault-mode VMs, xe_svm_init() additionally acquires the pagemap\nowner via drm_pagemap_acquire_owner() and the pagemaps via\nxe_svm_get_pagemaps(). Those resources are released by xe_svm_close(),\nnot xe_svm_fini(). On the same error path, xe_svm_close() is not\ncalled either, so fault-mode VMs leak the pagemap owner and pagemaps.\n\nFix both leaks:\n\n- Call xe_svm_fini() unconditionally on the err_svm_fini path, matching\n the unconditional xe_svm_init() call. Move the vm-\u003esize = 0\n assignment out of the conditional so the xe_vm_is_closed() assert in\n xe_svm_fini() (and xe_svm_close()) holds for both modes.\n\n- Call xe_svm_close() for fault-mode VMs before xe_svm_fini(), matching\n the ordering used in xe_vm_close_and_put().\n\n(cherry picked from commit ca2a3587d577ba764e0fe628fb676244fc33ddd4)",
"id": "GHSA-w7rf-7rxm-hr7v",
"modified": "2026-08-14T00:31:55Z",
"published": "2026-08-10T15:33:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68298"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/279339aa8bdcf9db40094cf2bcbd495c53dbe817"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9ac92736030f3395d970c300eaeb59ac258a0c3e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d2c6800ad1802bed72a6de1416536737f114f1d6"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.