{"api_version":"1","generated_at":"2026-08-25T16:15:15+00:00","cve":"CVE-2026-68298","urls":{"html":"https://cve.report/CVE-2026-68298","api":"https://cve.report/api/cve/CVE-2026-68298.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-68298","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-68298"},"summary":{"title":"drm/xe/vm: Fix SVM leak on resv obj alloc failure in xe_vm_create()","description":"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->svm.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->size = 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)","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-10 13:20:19","updated_at":"2026-08-17 05:18:32"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/9ac92736030f3395d970c300eaeb59ac258a0c3e","name":"https://git.kernel.org/stable/c/9ac92736030f3395d970c300eaeb59ac258a0c3e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/279339aa8bdcf9db40094cf2bcbd495c53dbe817","name":"https://git.kernel.org/stable/c/279339aa8bdcf9db40094cf2bcbd495c53dbe817","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/d2c6800ad1802bed72a6de1416536737f114f1d6","name":"https://git.kernel.org/stable/c/d2c6800ad1802bed72a6de1416536737f114f1d6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-68298","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68298","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9e978741488261e117bb50e5dfcf8e4080990958 279339aa8bdcf9db40094cf2bcbd495c53dbe817 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9e978741488261e117bb50e5dfcf8e4080990958 9ac92736030f3395d970c300eaeb59ac258a0c3e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9e978741488261e117bb50e5dfcf8e4080990958 d2c6800ad1802bed72a6de1416536737f114f1d6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.42 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.6 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"68298","cve":"CVE-2026-68298","epss":"0.001270000","percentile":"0.027760000","score_date":"2026-08-17","updated_at":"2026-08-18 00:11:47"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/xe/xe_vm.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"279339aa8bdcf9db40094cf2bcbd495c53dbe817","status":"affected","version":"9e978741488261e117bb50e5dfcf8e4080990958","versionType":"git"},{"lessThan":"9ac92736030f3395d970c300eaeb59ac258a0c3e","status":"affected","version":"9e978741488261e117bb50e5dfcf8e4080990958","versionType":"git"},{"lessThan":"d2c6800ad1802bed72a6de1416536737f114f1d6","status":"affected","version":"9e978741488261e117bb50e5dfcf8e4080990958","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/xe/xe_vm.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.18"},{"lessThan":"6.18","status":"unaffected","version":"0","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.18.42","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.6","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.18","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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->svm.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->size = 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)"}],"metrics":[{"cvssV3_1":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - Reached through the DRM_IOCTL_XE_VM_CREATE ioctl on /dev/dri/renderD*, which requires local access to the render node; there is no remote or network path into xe_vm_create().\nAC:L - The attacker induces the required drm_gpuvm_resv_object_alloc() ENOMEM by generating memory pressure while looping VM creates, and controls the second half of the bug directly by issuing another fault-mode VM create to walk the corrupted global peer list.\nPR:L - Any user with access to the render node (render/video group, typical for desktop, container, and Android GPU clients) can issue the ioctl; xe_vm_create_ioctl() performs no capability check.\nUI:N - The attacking process triggers the faulty error path entirely on its own via repeated ioctls; no action by another user is needed.\nS:U - The corruption stays within the kernel's own memory and security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The freed xe_vm stays linked in the global xe_owner_list, so later drm_pagemap_acquire_owner() walks read cur_peer->owner and dereference container_of() pointers out of a reclaimable slab object, giving an attacker who sprays that object a kernel read primitive.\nI:H - The dangling list node lets list_add_tail() write through attacker-reclaimed next/prev pointers in the freed xe_vm, a classic linked-list write primitive that can be escalated to control-flow hijack and privilege escalation.\nA:H - Traversing the global owner list through a freed xe_vm reliably oopses or panics the kernel, and the leaked pagemap owner and xe_pagemap references permanently pin device memory resources."}]}],"providerMetadata":{"dateUpdated":"2026-08-17T05:02:34.595Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/279339aa8bdcf9db40094cf2bcbd495c53dbe817"},{"url":"https://git.kernel.org/stable/c/9ac92736030f3395d970c300eaeb59ac258a0c3e"},{"url":"https://git.kernel.org/stable/c/d2c6800ad1802bed72a6de1416536737f114f1d6"}],"title":"drm/xe/vm: Fix SVM leak on resv obj alloc failure in xe_vm_create()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-68298","datePublished":"2026-08-10T12:02:32.194Z","dateReserved":"2026-07-30T09:28:09.380Z","dateUpdated":"2026-08-17T05:02:34.595Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-10 13:20:19","lastModifiedDate":"2026-08-17 05:18:32","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"68298","Ordinal":"1","Title":"drm/xe/vm: Fix SVM leak on resv obj alloc failure in xe_vm_creat","CVE":"CVE-2026-68298","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"68298","Ordinal":"1","NoteData":"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->svm.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->size = 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)","Type":"Description","Title":"drm/xe/vm: Fix SVM leak on resv obj alloc failure in xe_vm_creat"}]}}}