CVE-2026-89811: drm/amdkfd: Add TLB flush after MES queue eviction/suspension
drm/amdkfd: Add TLB flush after MES queue eviction/suspension
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Update the Linux kernel drm/amdkfd code to add kfd_flush_tlb() after MES queue removal in both specified locations: (1) after MES queue eviction removes all queues (in evict_process_queues_cpsch(): after all queues removed during eviction), and (2) after debug/criu queue suspension with mem_fence barrier (in suspend_queues(): after debug/criu queue suspension with mem_fence barrier) to ensure in-flight memory accesses from unmapped queues are flushed before memory is freed or migrated.
drm/amdkfd (Linux kernel) TLB flush after MES queue eviction/suspension = Add kfd_flush_tlb() calls after MES queue removal in two locations (after MES queue eviction and after queue suspension/debug-criu queue suspension with mem_fence barrier)
Event History
Frequently Asked Questions
Which hardware and configuration are known to exhibit this issue?
The issue is reported on gfx1151 (Strix Point) systems with XNACK mode 1 enabled. It occurs in the AMD KFD path when MES-managed GPU queues are involved in SVM page migration.
How can an affected system present operationally?
Affected systems can show KFDSVMRangeTest.MultiThreadMigrationTest failures, GPU compute queues with submitted packets that are never consumed, page faults, and GPU queue hangs.
Which queue-management operations are implicated?
The race is associated with MES queue eviction and suspension after queues are unmapped. In-flight DMA descriptors may still access the unmapped memory until a TLB flush is performed.