{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-80606","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-08-26T14:34:25.772Z","datePublished":"2026-08-28T06:48:30.960Z","dateUpdated":"2026-08-29T06:21:16.890Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-29T06:21:16.890Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe/userptr: Hold notifier_lock for write on inject test path\n\nWhen CONFIG_DRM_XE_USERPTR_INVAL_INJECT=y, xe_pt_svm_userptr_pre_commit()\nruns vma_check_userptr() with the svm notifier_lock taken for read. The\ntest injection causes vma_check_userptr() to call\nxe_vma_userptr_force_invalidate(), which feeds into\nxe_vma_userptr_do_inval() with drm_gpusvm_ctx.in_notifier=true. That\nflag tells drm_gpusvm_unmap_pages() the caller already holds\nnotifier_lock for write and only asserts the mode. Because the caller\nactually holds it for read, the assertion fires:\n\n  WARNING: drivers/gpu/drm/drm_gpusvm.c:1669 at \\\n           drm_gpusvm_unmap_pages+0xd4/0x130 [drm_gpusvm_helper]\n  Call Trace:\n   xe_vma_userptr_do_inval+0x40d/0xfd0 [xe]\n   xe_vma_userptr_invalidate_pass1+0x3e6/0x8d0 [xe]\n   xe_vma_userptr_force_invalidate+0xde/0x290 [xe]\n   vma_check_userptr.constprop.0+0x1c6/0x220 [xe]\n   xe_pt_svm_userptr_pre_commit+0x6a3/0xc60 [xe]\n   ...\n   xe_vm_bind_ioctl+0x3a0a/0x4480 [xe]\n\nAcquire notifier_lock for write in pre-commit when the inject Kconfig\nis enabled, via new helpers xe_pt_svm_userptr_notifier_lock()/_unlock().\nRename xe_svm_assert_held_read() to\nxe_svm_assert_held_read_or_inject_write() so it asserts the correct\nmode under each build configuration. Production builds\n(CONFIG_DRM_XE_USERPTR_INVAL_INJECT=n) keep the existing read-mode\nbehavior bit-for-bit.\n\n(cherry picked from commit 80ccbd97ffee8ad2e73167d826fe7be548364365)"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The bug is reached only through DRM_IOCTL_XE_VM_BIND on a local /dev/dri/renderD* character device; there is no network, adjacent-radio, or physical-bus attack surface on this code path.\nAC:H - Exploitation requires CONFIG_DRM_XE_USERPTR_INVAL_INJECT=y (debug-only Kconfig default n), Intel Xe hardware with drm/xe loaded, and CONFIG_DRM_GPUSVM—rare non-default conditions beyond typical attacker control on production systems.\nPR:L - Any unprivileged local user who can open the DRM render node can create a VM and issue XE_VM_BIND userptr map/remap operations to drive the inject path; root or init-namespace admin rights are not required.\nUI:N - Exploitation requires only attacker-issued GPU bind ioctls against their own VM; no victim user or administrator must perform any separate action.\nS:C - The racy unmap tears down IOMMU/DMA mappings without exclusive notifier_lock, allowing the GPU to access host memory outside the attacker's intended userptr mapping and crossing the device/kernel memory isolation boundary.\nC:H - Concurrent drm_gpusvm_unmap_pages() under a read notifier_lock races with other userptr/SVM accessors, enabling use-after-free of GPU SVM page state and arbitrary kernel memory disclosure.\nI:H - Unsafe concurrent DMA unmap and pagemap teardown corrupts GPU SVM mapping metadata under weak locking, which can be leveraged for controlled kernel memory writes and code execution.\nA:H - The bug triggers a kernel WARNING/oops via lockdep_assert_held_write() in drm_gpusvm_unmap_pages() and can panic or wedge the Xe driver from unsafe concurrent userptr invalidation."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/xe/xe_pt.c","drivers/gpu/drm/xe/xe_svm.h"],"versions":[{"version":"9e978741488261e117bb50e5dfcf8e4080990958","lessThan":"f9a9abd7bbdab3dfe1b1155e1457dc02b5e14ea5","status":"affected","versionType":"git"},{"version":"9e978741488261e117bb50e5dfcf8e4080990958","lessThan":"ab9ea5c943c7e780124e75b7ffad9f1c752b2579","status":"affected","versionType":"git"},{"version":"9e978741488261e117bb50e5dfcf8e4080990958","lessThan":"dca6e08c923a44d2d66b955e03dd57a3a38c2b94","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/xe/xe_pt.c","drivers/gpu/drm/xe/xe_svm.h"],"versions":[{"version":"6.18","status":"affected"},{"version":"0","lessThan":"6.18","status":"unaffected","versionType":"semver"},{"version":"6.18.40","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.1.5","lessThanOrEqual":"7.1.*","status":"unaffected","versionType":"semver"},{"version":"7.2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.18","versionEndExcluding":"6.18.40"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.18","versionEndExcluding":"7.1.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.18","versionEndExcluding":"7.2"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/f9a9abd7bbdab3dfe1b1155e1457dc02b5e14ea5"},{"url":"https://git.kernel.org/stable/c/ab9ea5c943c7e780124e75b7ffad9f1c752b2579"},{"url":"https://git.kernel.org/stable/c/dca6e08c923a44d2d66b955e03dd57a3a38c2b94"}],"title":"drm/xe/userptr: Hold notifier_lock for write on inject test path","x_generator":{"engine":"bippy-1.2.0"}}}}