CVE-2026-68232: drm/gpusvm: Fix MM reference leak in drm_gpusvm_range_evict
Greg Kroah-Hartman <[email protected]>
| Newsgroups | org.kernel.vger.linux-cve-announce |
|---|---|
| Message-ID | <2026081017-CVE-2026-68232-1fca@gregkh> |
From: Greg Kroah-Hartman <[email protected]> Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/gpusvm: Fix MM reference leak in drm_gpusvm_range_evict If kvmalloc_array() fails in drm_gpusvm_range_evict(), the MM reference acquired earlier is not released, resulting in a reference leak. Fix this by dropping the MM reference on the kvmalloc_array() failure path. The Linux kernel CVE team has assigned CVE-2026-68232 to this issue. Affected and fixed versions =========================== Issue introduced in 6.15 with commit 99624bdff8670795b678eafa6509aaad3a5c0175 and fixed in 6.18.42 with commit a2212fef8e18724e06432fce01fa257296d9f053 Issue introduced in 6.15 with commit 99624bdff8670795b678eafa6509aaad3a5c0175 and fixed in 7.1.6 with commit adf0542659c783c962f4a8f2adcb3532ed54821c Issue introduced in 6.15 with commit 99624bdff8670795b678eafa6509aaad3a5c0175 and fixed in 7.2-rc5 with commit 847b371debf3c8c72384ab7b9a0c4123a74cc925 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-68232 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/gpu/drm/drm_gpusvm.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/a2212fef8e18724e06432fce01fa257296d9f053 https://git.kernel.org/stable/c/adf0542659c783c962f4a8f2adcb3532ed54821c https://git.kernel.org/stable/c/847b371debf3c8c72384ab7b9a0c4123a74cc925