CVE-2026-43318 (GCVE-0-2026-43318)
Vulnerability from cvelistv5 – Published: 2026-05-08 13:26 – Updated: 2026-05-08 13:26
VLAI?
Title
drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify
Summary
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.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Linux | Linux |
Affected:
a448cb003edcb4b63d0a9c95f3faab724e6150fb , < 82a7ea35a1526bef8ae170c33ff80e5db7728961
(git)
Affected: a448cb003edcb4b63d0a9c95f3faab724e6150fb , < 89a9389ad70d3c69538e59d87df67d407aef4c26 (git) Affected: a448cb003edcb4b63d0a9c95f3faab724e6150fb , < 3307459eb3583115264421e859858d1f90f3694a (git) Affected: a448cb003edcb4b63d0a9c95f3faab724e6150fb , < b18fc0ab837381c1a6ef28386602cd888f2d9edf (git) |
||
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "82a7ea35a1526bef8ae170c33ff80e5db7728961",
"status": "affected",
"version": "a448cb003edcb4b63d0a9c95f3faab724e6150fb",
"versionType": "git"
},
{
"lessThan": "89a9389ad70d3c69538e59d87df67d407aef4c26",
"status": "affected",
"version": "a448cb003edcb4b63d0a9c95f3faab724e6150fb",
"versionType": "git"
},
{
"lessThan": "3307459eb3583115264421e859858d1f90f3694a",
"status": "affected",
"version": "a448cb003edcb4b63d0a9c95f3faab724e6150fb",
"versionType": "git"
},
{
"lessThan": "b18fc0ab837381c1a6ef28386602cd888f2d9edf",
"status": "affected",
"version": "a448cb003edcb4b63d0a9c95f3faab724e6150fb",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.7"
},
{
"lessThan": "5.7",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.75",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.16",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.75",
"versionStartIncluding": "5.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.16",
"versionStartIncluding": "5.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.6",
"versionStartIncluding": "5.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0",
"versionStartIncluding": "5.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify\n\nInvalidating a dmabuf will impact other users of the shared BO.\nIn the scenario where process A moves the BO, it needs to inform\nprocess B about the move and process B will need to update its\npage table.\n\nThe commit fixes a synchronisation bug caused by the use of the\nticket: it made amdgpu_vm_handle_moved behave as if updating\nthe page table immediately was correct but in this case it\u0027s not.\n\nAn example is the following scenario, with 2 GPUs and glxgears\nrunning on GPU0 and Xorg running on GPU1, on a system where P2P\nPCI isn\u0027t supported:\n\nglxgears:\n export linear buffer from GPU0 and import using GPU1\n submit frame rendering to GPU0\n submit tiled-\u003elinear blit\nXorg:\n copy of linear buffer\n\nThe sequence of jobs would be:\n drm_sched_job_run # GPU0, frame rendering\n drm_sched_job_queue # GPU0, blit\n drm_sched_job_done # GPU0, frame rendering\n drm_sched_job_run # GPU0, blit\n move linear buffer for GPU1 access #\n amdgpu_dma_buf_move_notify -\u003e update pt # GPU0\n\nIt this point the blit job on GPU0 is still running and would\nlikely produce a page fault."
}
],
"providerMetadata": {
"dateUpdated": "2026-05-08T13:26:13.557Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/82a7ea35a1526bef8ae170c33ff80e5db7728961"
},
{
"url": "https://git.kernel.org/stable/c/89a9389ad70d3c69538e59d87df67d407aef4c26"
},
{
"url": "https://git.kernel.org/stable/c/3307459eb3583115264421e859858d1f90f3694a"
},
{
"url": "https://git.kernel.org/stable/c/b18fc0ab837381c1a6ef28386602cd888f2d9edf"
}
],
"title": "drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-43318",
"datePublished": "2026-05-08T13:26:13.557Z",
"dateReserved": "2026-05-01T14:12:56.001Z",
"dateUpdated": "2026-05-08T13:26:13.557Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2026-43318\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-05-08T14:16:40.363\",\"lastModified\":\"2026-05-08T14:16:40.363\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify\\n\\nInvalidating a dmabuf will impact other users of the shared BO.\\nIn the scenario where process A moves the BO, it needs to inform\\nprocess B about the move and process B will need to update its\\npage table.\\n\\nThe commit fixes a synchronisation bug caused by the use of the\\nticket: it made amdgpu_vm_handle_moved behave as if updating\\nthe page table immediately was correct but in this case it\u0027s not.\\n\\nAn example is the following scenario, with 2 GPUs and glxgears\\nrunning on GPU0 and Xorg running on GPU1, on a system where P2P\\nPCI isn\u0027t supported:\\n\\nglxgears:\\n export linear buffer from GPU0 and import using GPU1\\n submit frame rendering to GPU0\\n submit tiled-\u003elinear blit\\nXorg:\\n copy of linear buffer\\n\\nThe sequence of jobs would be:\\n drm_sched_job_run # GPU0, frame rendering\\n drm_sched_job_queue # GPU0, blit\\n drm_sched_job_done # GPU0, frame rendering\\n drm_sched_job_run # GPU0, blit\\n move linear buffer for GPU1 access #\\n amdgpu_dma_buf_move_notify -\u003e update pt # GPU0\\n\\nIt this point the blit job on GPU0 is still running and would\\nlikely produce a page fault.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/3307459eb3583115264421e859858d1f90f3694a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/82a7ea35a1526bef8ae170c33ff80e5db7728961\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/89a9389ad70d3c69538e59d87df67d407aef4c26\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b18fc0ab837381c1a6ef28386602cd888f2d9edf\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…