CVE-2026-43318: drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: fix sync handling in amdgpudmabufmovenotify
Invalidating a dmabuf will impact other users of the shared BO. In the scenario where process A moves the BO, it needs to inform process B about the move and process B will need to update its page table.
The commit fixes a synchronisation bug caused by the use of the ticket: it made amdgpuvmhandlemoved behave as if updating the page table immediately was correct but in this case it's not.
An example is the following scenario, with 2 GPUs and glxgears running on GPU0 and Xorg running on GPU1, on a system where P2P PCI isn't supported:
glxgears: export linear buffer from GPU0 and import using GPU1 submit frame rendering to GPU0 submit tiled->linear blit Xorg: copy of linear buffer
The sequence of jobs would be: drmschedjobrun # GPU0, frame rendering drmschedjobqueue # GPU0, blit drmschedjobdone # GPU0, frame rendering drmschedjobrun # GPU0, blit move linear buffer for GPU1 access # amdgpudmabufmovenotify -> update pt # GPU0
It this point the blit job on GPU0 is still running and would likely produce a page fault.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43318?
CVE-2026-43318 has a medium severity rating of 5.5 according to the CVSS 3.1 metrics.
How do I fix CVE-2026-43318?
To fix CVE-2026-43318, apply the available patches provided for the Linux kernel and amdgpu.
What is the impact of CVE-2026-43318?
CVE-2026-43318 can lead to improper synchronization handling when managing shared buffer objects in the Linux kernel.
Which systems are affected by CVE-2026-43318?
CVE-2026-43318 affects systems running the Linux kernel with the amdgpu driver.
When was CVE-2026-43318 published?
CVE-2026-43318 was published on May 8, 2026.