CVE-2026-99625: drm/amdgpu: Fix duplicate dependency fence releases
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Fix duplicate dependency fence releases
drmschedjobadddependency() consumes its fence reference on success and failure. Do not release the fence again if drmschedjobadddependency() fails.
(cherry picked from commit e04f3dfb2071451633e6440a3911a9bb65df9144)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 7.3.5-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch e04f3dfb2071451633e6440a3911a9bb65df9144
Event History
Frequently Asked Questions
What component is affected?
The issue is in the Linux kernel's AMDGPU DRM driver, specifically its handling of dependency fence references during scheduler job dependency setup.
What condition triggers the bug?
The bug is triggered when drm_sched_job_add_dependency() fails and the caller releases a dependency fence reference that the function has already consumed. This results in a duplicate fence release.
How is the issue fixed?
The fix removes the additional fence release after drm_sched_job_add_dependency() fails, because that function consumes the fence reference on both successful and failed calls.