CVE-2026-99627: Linux kernel · drm/amdgpu/gfx12: disallow GFXOFF while updating the SPM VMID
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d1551515a3258b43cba60bd7f45bbdd1f4e9e60a : update Linux kernel when convenient.
Data as of 20 Nov 2026, 06:04 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in d1551515a3258b43cba60bd7f45bbdd1f4e9e60a, cd38a2b45edf84324ee9572c09c279fd4ebec5fc, 374aba4bef461462a9640f8355ebff5d5021c459 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 d1551515a3258b43cba60bd7f45bbdd1f4e9e60a, cd38a2b45edf84324ee9572c09c279fd4ebec5fc, 374aba4bef461462a9640f8355ebff5d5021c459 or 117e6ac89e730d647aeaf53b77420efece331f4d.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/gfx12: disallow GFXOFF while updating the SPM VMID gfx_v12_0_update_spm_vmid() does a read-modify-write of RLC_SPM_MC_CNTL over MMIO without keeping GFX powered, unlike gfx11. When GFX is in GFXOFF at that point the update doesn't stick, and with the SPM VMID programmed on submission again, the job of a process with a reserved VMID can still run with the SPM writing through VMID 0. On navi48, after a few other submissions and a VM fault on the same VM, a COPY_DATA of RLC_SPM_MC_CNTL from such a job reads 0 although the update was called for it: $ amd_uapi_regression --run-subtest cs-secure-ib-compute,gem-mapping-info-high-va,gpuvm-fault-high-va,reserved-vmid-spm-vmid amdgpu 0000:03:00.0: [gfxhub] page fault (src_id:0 ring:40 vmid:7 pasid:185) amdgpu 0000:03:00.0: Faulty UTCL2 client ID: SDMA1 (0xe) RLC_SPM_MC_CNTL in the job: 0x00000000 With GFXOFF disallowed around the update it reads the reserved VMID 15. (cherry picked from commit 907aebc5578ae09fa5c0e2f0784201295837e60b)
References
- git.kernel.org/stable/c/117e6ac89e730d647aeaf53b77420efece331f4d (opens in a new tab)
- git.kernel.org/stable/c/cd38a2b45edf84324ee9572c09c279fd4ebec5fc (opens in a new tab)
- git.kernel.org/stable/c/374aba4bef461462a9640f8355ebff5d5021c459 (opens in a new tab)
- git.kernel.org/stable/c/d1551515a3258b43cba60bd7f45bbdd1f4e9e60a (opens in a new tab)