UBUNTU-CVE-2026-68298: Low severity ubuntu/linux-hwe-edge vulnerability
In the Linux kernel, the following vulnerability has been resolved: drm/xe/vm: Fix SVM leak on resv obj alloc failure in xevmcreate() Commit 9e9787414882 ("drm/xe/userptr: replace xehmm with gpusvm") made xesvminit() unconditional in xevmcreate() and extended it to also initialize a "simple" gpusvm state for non-fault-mode VMs. The matching xesvmfini() call in xevmcloseandput() was updated to run unconditionally, but the error unwind path in xevmcreate() was not. On the drmgpuvmresvobjectalloc() failure path, xesvminit() has already succeeded but xesvmfini() is only called when XEVMFLAGFAULTMODE is set. For non-fault-mode VMs this leaves vm->svm.gpusvm partially initialized and leaks the resources allocated by drmgpusvminit(). For fault-mode VMs, xesvminit() additionally acquires the pagemap owner via drmpagemapacquireowner() and the pagemaps via xesvmgetpagemaps(). Those resources are released by xesvmclose(), not xesvmfini(). On the same error path, xesvmclose() is not called either, so fault-mode VMs leak the pagemap owner and pagemaps. Fix both leaks: - Call xesvmfini() unconditionally on the errsvmfini path, matching the unconditional xesvminit() call. Move the vm->size = 0 assignment out of the conditional so the xevmisclosed() assert in xesvmfini() (and xesvmclose()) holds for both modes. - Call xesvmclose() for fault-mode VMs before xesvmfini(), matching the ordering used in xevmcloseandput(). (cherry picked from commit ca2a3587d577ba764e0fe628fb676244fc33ddd4)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-aws-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fde-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1016.16~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38~24.04.4 - Upgrade
Upgrade
ubuntu/linux-nvidia-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1024.25~24.04.1 - Upgrade
Upgrade
ubuntu/linux-oracle-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1013.13~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-38.38 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.0.0-1016.16 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1008.9 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-nvidia-bosto a version that resolves this vulnerability.Fixed in 7.0.0-2022.23 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch ca2a3587d577ba764e0fe628fb676244fc33ddd4
Event History
Frequently Asked Questions
What level of access is required to exploit this issue?
The supplied vector indicates local access with low privileges is required. No user interaction is required.
Are both fault-mode and non-fault-mode VM configurations exposed to the resource leak?
Yes. Non-fault-mode VMs can leak partially initialized gpusvm resources, while fault-mode VMs can additionally leak the pagemap owner and pagemaps when reservation-object allocation fails.
Which Ubuntu kernel package variants are listed for this CVE?
The listed variants are linux-riscv, linux-realtime, linux-hwe-edge, linux-azure, linux-gcp, linux-azure-fde, linux-gke, and linux-aws-5.0.