Bug 2461451 (CVE-2026-31566) - CVE-2026-31566 kernel: drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib
Summary: CVE-2026-31566 kernel: drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd...
Keywords:
Status: NEW
Alias: CVE-2026-31566
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-24 15:02 UTC by OSIDB Bzimport
Modified: 2026-09-24 05:25 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:67150 0 None None None 2026-09-14 13:35:30 UTC
Red Hat Product Errata RHSA-2026:67471 0 None None None 2026-09-15 06:14:18 UTC
Red Hat Product Errata RHSA-2026:71329 0 None None None 2026-09-24 05:25:18 UTC
Red Hat Product Errata RHSA-2026:71330 0 None None None 2026-09-24 04:32:42 UTC

Description OSIDB Bzimport 2026-04-24 15:02:13 UTC
In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib

amdgpu_amdkfd_submit_ib() submits a GPU job and gets a fence
from amdgpu_ib_schedule(). This fence is used to wait for job
completion.

Currently, the code drops the fence reference using dma_fence_put()
before calling dma_fence_wait().

If dma_fence_put() releases the last reference, the fence may be
freed before dma_fence_wait() is called. This can lead to a
use-after-free.

Fix this by waiting on the fence first and releasing the reference
only after dma_fence_wait() completes.

Fixes the below:
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:697 amdgpu_amdkfd_submit_ib() warn: passing freed memory 'f' (line 696)

(cherry picked from commit 8b9e5259adc385b61a6590a13b82ae0ac2bd3482)

Comment 8 Jon Orris 2026-09-14 13:35:29 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:67150 https://access.redhat.com/errata/RHSA-2026:67150

Comment 9 Jon Orris 2026-09-15 06:14:17 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:67471 https://access.redhat.com/errata/RHSA-2026:67471

Comment 10 Jon Orris 2026-09-24 04:32:41 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:71330 https://access.redhat.com/errata/RHSA-2026:71330

Comment 11 Jon Orris 2026-09-24 05:25:16 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:71329 https://access.redhat.com/errata/RHSA-2026:71329


Note You need to log in before you can comment on or make changes to this bug.