VulnerabilityPublished 8 May 2026Updated 6 Nov 2026

CVE-2026-43318: Linux kernel · drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in b18fc0ab837381c1a6ef28386602cd888f2d9edf : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:04 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in b18fc0ab837381c1a6ef28386602cd888f2d9edf, 3307459eb3583115264421e859858d1f90f3694a, 89a9389ad70d3c69538e59d87df67d407aef4c26 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to b18fc0ab837381c1a6ef28386602cd888f2d9edf, 3307459eb3583115264421e859858d1f90f3694a, 89a9389ad70d3c69538e59d87df67d407aef4c26 or 82a7ea35a1526bef8ae170c33ff80e5db7728961.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ a448cb003edcb4b63d0a9c95f3faab724e6150fb, < b18fc0ab837381c1a6ef28386602cd888f2d9edf	Fixed in b18fc0ab837381c1a6ef28386602cd888f2d9edf
LinuxLinux	Affected ≥ a448cb003edcb4b63d0a9c95f3faab724e6150fb, < 3307459eb3583115264421e859858d1f90f3694a	Fixed in 3307459eb3583115264421e859858d1f90f3694a
LinuxLinux	Affected ≥ a448cb003edcb4b63d0a9c95f3faab724e6150fb, < 89a9389ad70d3c69538e59d87df67d407aef4c26	Fixed in 89a9389ad70d3c69538e59d87df67d407aef4c26
LinuxLinux	Affected ≥ a448cb003edcb4b63d0a9c95f3faab724e6150fb, < 82a7ea35a1526bef8ae170c33ff80e5db7728961	Fixed in 82a7ea35a1526bef8ae170c33ff80e5db7728961
LinuxLinux	Affected =5.7	Fixed in–

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.

References

Community reviews

Loading reviews…