Skip to main content
VulnerabilityPublished

CVE-2026-99621: Linux kernel · drm/amdgpu: unlock the VM and BO when attaching a KFD BO fails

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to e0a1404b34e0002f03f7979cdb791a9b5c3963f5 or 1ae594845217ce740b27ec5a202e9e8cb144e0aa when convenient.

Data as of 20 Nov 2026, 06:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in e0a1404b34e0002f03f7979cdb791a9b5c3963f5, 1ae594845217ce740b27ec5a202e9e8cb144e0aa

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade Linux kernel to e0a1404b34e0002f03f7979cdb791a9b5c3963f5 or 1ae594845217ce740b27ec5a202e9e8cb144e0aa.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ fd1fa48b935f22c7d99713bf33846e14a6bb6ab9, < e0a1404b34e0002f03f7979cdb791a9b5c3963f5
Fixed in
  • e0a1404b34e0002f03f7979cdb791a9b5c3963f5
LinuxLinuxAffected
  • ≥ fd1fa48b935f22c7d99713bf33846e14a6bb6ab9, < 1ae594845217ce740b27ec5a202e9e8cb144e0aa
Fixed in
  • 1ae594845217ce740b27ec5a202e9e8cb144e0aa
LinuxLinuxAffected
  • =7.0
Fixed in–

Description

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)

References

Community reviews

Loading reviews…