Bug 2577653 (CVE-2026-99621) - CVE-2026-99621 kernel: kernel: amdgpu: Denial of Service via improper lock cleanup in kfd_mem_attach()
Summary: CVE-2026-99621 kernel: kernel: amdgpu: Denial of Service via improper lock cl...
Keywords:
Status: NEW
Alias: CVE-2026-99621
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 06:06 UTC by OSIDB Bzimport
Modified: 2026-11-20 10:03 UTC (History)
17 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 06:06:28 UTC
In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: unlock the VM and BO when attaching a KFD BO fails

kfd_mem_attach() locks the page directory and the BO with a drm_exec
transaction on its stack, but leaves through the unwind label without
drm_exec_fini() when locking fails, e.g. when MAP_MEMORY_TO_GPU gets a
signal while the page directory or the BO is busy. Reservations already
acquired then remain locked with their ww_acquire_ctx pointing into the
expired stack frame.

With one thread doing GEM_VA map/unmap on the KFD VM and
another one mapping KFD BOs while getting SIGUSR1 every 20 us:

  BUG: KASAN: stack-out-of-bounds in __ww_mutex_lock.constprop.0+0x34f5/0x3da0
   ww_mutex_lock_interruptible+0x2f/0x150
   drm_exec_lock_obj+0x107/0x2d0 [drm_exec]
   kfd_mem_attach+0x4dd/0x1b60 [amdgpu]

and the process ends up in D state.

Finish the transaction before unwinding.

(cherry picked from commit 7b885fa27e4b9fa5cbdc64e66fc35872aee296f5)


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