In the Linux kernel, the following vulnerability has been resolved: drm/xe/userptr: Hold notifier_lock for write on inject test path When CONFIG_DRM_XE_USERPTR_INVAL_INJECT=y, xe_pt_svm_userptr_pre_commit() runs vma_check_userptr() with the svm notifier_lock taken for read. The test injection causes vma_check_userptr() to call xe_vma_userptr_force_invalidate(), which feeds into xe_vma_userptr_do_inval() with drm_gpusvm_ctx.in_notifier=true. That flag tells drm_gpusvm_unmap_pages() the caller already holds notifier_lock for write and only asserts the mode. Because the caller actually holds it for read, the assertion fires: WARNING: drivers/gpu/drm/drm_gpusvm.c:1669 at \ drm_gpusvm_unmap_pages+0xd4/0x130 [drm_gpusvm_helper] Call Trace: xe_vma_userptr_do_inval+0x40d/0xfd0 [xe] xe_vma_userptr_invalidate_pass1+0x3e6/0x8d0 [xe] xe_vma_userptr_force_invalidate+0xde/0x290 [xe] vma_check_userptr.constprop.0+0x1c6/0x220 [xe] xe_pt_svm_userptr_pre_commit+0x6a3/0xc
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-80606 is a lock ordering vulnerability in the Linux kernel's DRM/XE graphics driver, specifically in the userptr (user space pointer) memory management subsystem. When test injection is enabled via CONFIG_DRM_XE_USERPTR_INVAL_INJECT, a code path attempts to acquire a write lock while already holding a read lock on the same notifier_lock, creating a potential deadlock condition. This affects Linux systems running the XE GPU driver with test configurations enabled, particularly in containerized environments and cloud deployments where GPU passthrough or sharing is utilized. The vulnerability has a CVSS score of 7.8 (high), indicating significant impact potential through denial of service scenarios.
While this CVE currently maps to zero MITRE ATT&CK techniques and lacks CISA KEV status, Casky's extended reasoning capabilities would detect the underlying resource contention pattern characteristic of T1499 (Resource Exhaustion) attacks. A practitioner monitoring kernel behavior would observe lock contention spikes, process hangs in GPU memory validation routines, and potential system resource starvation during GPU memory operations. Casky's 754 mapped security skills enable detection of suspicious synchronization patterns in kernel logs and GPU driver operations—specifically anomalous lock acquisition sequences and elevated context-switch rates that indicate the notifier_lock ordering violation being exploited or triggered unexpectedly.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-80606. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation