CVE-2026-43318
Last modified
CVE-2026-43318 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify 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 amdgpu_vm_handle_moved 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: drm_sched_job_run # GPU0, frame rendering drm_sched_job_queue # GPU0, blit drm_sched_job_done # GPU0, frame rendering drm_sched_job_run # GPU0, blit move linear buffer for GPU1 access # amdgpu_dma_buf_move_notify -> update pt # GPU0 It this point the blit job on GPU0 is still running and would likely produce a page fault.. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify 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 amdgpu_vm_handle_moved 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: drm_sched_job_run # GPU0, frame rendering drm_sched_job_queue # GPU0, blit drm_sched_job_done # GPU0, frame rendering drm_sched_job_run # GPU0, blit move linear buffer for GPU1 access # amdgpu_dma_buf_move_notify -> update pt # GPU0 It this point the blit job on GPU0 is still running and would likely produce a page fault.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.7, < 6.12.75 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.16 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.6 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-43318?
How severe is CVE-2026-43318?
How do I fix CVE-2026-43318?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-43312In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43313In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43314In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43315In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43316In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43317In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43319In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-4332GitLab has remediated an issue in GitLab EE affecting all ve…5.4
- CVE-2026-43320In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43321In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43322In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-43323In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-43318?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
