# CVE-2026-99627: drm/amdgpu/gfx12: disallow GFXOFF while updating the SPM VMID

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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)

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 52cb80c12e8a647aa9c903903d58916e6c1c4d38; < 117e6ac89e730d647aeaf53b77420efece331f4d (affected, git); ≥ 52cb80c12e8a647aa9c903903d58916e6c1c4d38; < cd38a2b45edf84324ee9572c09c279fd4ebec5fc (affected, git); ≥ 52cb80c12e8a647aa9c903903d58916e6c1c4d38; < 374aba4bef461462a9640f8355ebff5d5021c459 (affected, git); ≥ 52cb80c12e8a647aa9c903903d58916e6c1c4d38; < d1551515a3258b43cba60bd7f45bbdd1f4e9e60a (affected, git). Source: CNA: Linux
- Linux / Linux: 6.11 (affected); ≥ 0; < 6.11 (unaffected, semver); ≥ 6.12.118; ≤ 6.12.* (unaffected, semver); ≥ 6.18.64; ≤ 6.18.* (unaffected, semver); ≥ 7.3.5; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7.1 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7.1 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.17% as of 2026-11-21; percentile 6.19%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/117e6ac89e730d647aeaf53b77420efece331f4d (CNA: Linux)

- https://git.kernel.org/stable/c/cd38a2b45edf84324ee9572c09c279fd4ebec5fc (CNA: Linux)

- https://git.kernel.org/stable/c/374aba4bef461462a9640f8355ebff5d5021c459 (CNA: Linux)

- https://git.kernel.org/stable/c/d1551515a3258b43cba60bd7f45bbdd1f4e9e60a (CNA: Linux)

- https://git.kernel.org/stable/c/117e6ac89e730d647aeaf53b77420efece331f4d (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/374aba4bef461462a9640f8355ebff5d5021c459 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/cd38a2b45edf84324ee9572c09c279fd4ebec5fc (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/d1551515a3258b43cba60bd7f45bbdd1f4e9e60a (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99627; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99627; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99627; retrieved 2026-11-22; source updated Not reported

Revision: 02239823f2f0b34af43dab711e9d849fb2c4d501c1c0a43ef53a5ac20359c5ee

Canonical: https://y2.dev/cve/CVE-2026-99627

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.