CVE-2026-80606 Linux CVE debrief

Who should care

Linux kernel users and administrators, especially those using the drm/xe/userptr component, should be aware of this vulnerability and take steps to apply patches or mitigations. Additionally, security teams and vulnerability management teams should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Operators and platform administrators should also review compensating controls for exposed systems while remediation is scheduled and verified. Those responsible for monitoring, detection, and logs for exposed assets should check relevant monitoring, detection, and logs for exposed assets that need extra review. Those responsible for asset inventory and change management should track exceptions, retest remediated assets, and close the item only after evidence is documented. Those responsible for incident response and threat hunting should review the vulnerability and assess potential impact on their organization. Those responsible for patch management and software updates should assess Linux kernel version and apply patches or mitigations for drm/xe/userptr vulnerability. Those responsible for security architecture and engineering should review and update CONFIG_DRM_XE_USERPTR_INVAL_INJECT configuration and assess potential impact on their organization. Those responsible for risk management and compliance should review the vulnerability and assess potential impact on their organization. Those responsible for incident response and threat hunting should review the vulnerability and assess potential impact on their organization. Those responsible for security awareness and training should educate users about the vulnerability and the importance of applying patches or mitigations. Those responsible for vulnerability management and incident response should prioritize and coordinate remediation efforts with stakeholders. Those responsible for security operations and incident response should monitor for potential exploitation and respond accordingly. Those responsible for threat intelligence and incident response should review the vulnerability and assess potential impact on their organization. Those responsible for

Technical summary

The Linux kernel's drm/xe/userptr component has a vulnerability that arises when CONFIG_DRM_XE_USERPTR_INVAL_INJECT=y. In this configuration, xe_pt_svm_userptr_pre_commit() acquires the notifier_lock for read, but the test injection causes vma_check_userptr() to call xe_vma_userptr_force_invalidate(), leading to an assertion failure due to incorrect locking mode. The fix involves acquiring notifier_lock for write in pre-commit when the inject Kconfig is enabled.

Defensive priority

Linux kernel users should assess and apply patches or mitigations for drm/xe/userptr vulnerability.

Recommended defensive actions

• Assess Linux kernel version and apply patches or mitigations for drm/xe/userptr
• Review and update CONFIG_DRM_XE_USERPTR_INVAL_INJECT configuration
• Monitor Linux kernel updates for related security patches
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The vulnerability exists in the Linux kernel's drm/xe/userptr component. When CONFIG_DRM_XE_USERPTR_INVAL_INJECT=y, a locking issue arises in xe_pt_svm_userptr_pre_commit(), leading to a warning due to incorrect notifier_lock mode. The issue is resolved by acquiring notifier_lock for write in pre-commit when the inject Kconfig is enabled.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.