GPU VulnDB

Database/NVIDIA / GPU stack

Linux kernel drm_gpusvm: device mapping leak on the error path of drm_gpusvm_get_pages()

CVSS 8.8CVE-2026-68240NVIDIA / GPU stackcurated

Impact

drm_gpusvm_get_pages() only recorded the device pagemap on success, so when a later page failed (for example -EOPNOTSUPP with ctx->allow_mixed clear) the unmap path saw a NULL dpagemap and skipped device_unmap(), leaving the device mappings already created in place. On a GPU node this is a resource leak in the shared-virtual-memory path used by GPU compute workloads: repeated failing allocations accumulate leaked device mappings, and reclaiming them needs the driver reloaded or the node rebooted. The record describes a leak on an error path, not a confirmed memory-corruption or cross-tenant read primitive, and the fix is a one-line assignment. The NVD score of 8.8 is the Linux CNA's blanket value and is not backed by any described exploitation path.

Who can reach it

Local user with access to a GPU device node that drives the gpusvm path, able to trigger the failing-page case repeatedly. Authentication to the node is required; no remote or network path.

What to do

Pick up the stable kernels carrying the fix (three stable commits are linked) and reboot each affected GPU node; the change is in the DRM GPU SVM core, so it cannot be hot-patched or applied by restarting a daemon. Nodes running a kernel without drm_gpusvm, or without accelerators using it, are not affected. No vendor advisory with fixed version strings is present in the record beyond the kernel git commits.

References

Related entries

All NVIDIA / GPU stack entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.