CVE-2026-43318drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected a448cb003edcb4b63d0a9c95f3faab724e6150fb – < 82a7ea35a1526bef8ae170c33ff80e5db7728961
- affected a448cb003edcb4b63d0a9c95f3faab724e6150fb – < 89a9389ad70d3c69538e59d87df67d407aef4c26
- affected a448cb003edcb4b63d0a9c95f3faab724e6150fb – < 3307459eb3583115264421e859858d1f90f3694a
- affected a448cb003edcb4b63d0a9c95f3faab724e6150fb – < b18fc0ab837381c1a6ef28386602cd888f2d9edf
- affected 5.7
- unaffected < 5.7
- unaffected 6.12.75 – ≤ 6.12.*
- unaffected 6.18.16 – ≤ 6.18.*
- unaffected 6.19.6 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References4
- https://git.kernel.org/stable/c/82a7ea35a1526bef8ae170c33ff80e5db7728961 (opens in a new tab)
- https://git.kernel.org/stable/c/89a9389ad70d3c69538e59d87df67d407aef4c26 (opens in a new tab)
- https://git.kernel.org/stable/c/3307459eb3583115264421e859858d1f90f3694a (opens in a new tab)
- https://git.kernel.org/stable/c/b18fc0ab837381c1a6ef28386602cd888f2d9edf (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-28602 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43318)Record last updated .