GHSA-23V5-2H3W-J9HF

Vulnerability from github – Published: 2026-11-20 06:32 – Updated: 2026-11-20 06:32
VLAI
Details

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)

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99627"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-20T06:17:55Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu/gfx12: disallow GFXOFF while updating the SPM VMID\n\ngfx_v12_0_update_spm_vmid() does a read-modify-write of RLC_SPM_MC_CNTL\nover MMIO without keeping GFX powered, unlike gfx11. When GFX is in\nGFXOFF at that point the update doesn\u0027t stick, and with the SPM VMID\nprogrammed on submission again, the job of a process with a reserved\nVMID can still run with the SPM writing through VMID 0.\n\nOn navi48, after a few other submissions and a VM fault on the same VM,\na COPY_DATA of RLC_SPM_MC_CNTL from such a job reads 0 although the\nupdate was called for it:\n\n  $ amd_uapi_regression --run-subtest cs-secure-ib-compute,gem-mapping-info-high-va,gpuvm-fault-high-va,reserved-vmid-spm-vmid\n  amdgpu 0000:03:00.0: [gfxhub] page fault (src_id:0 ring:40 vmid:7 pasid:185)\n  amdgpu 0000:03:00.0: \t Faulty UTCL2 client ID: SDMA1 (0xe)\n  RLC_SPM_MC_CNTL in the job: 0x00000000\n\nWith GFXOFF disallowed around the update it reads the reserved VMID 15.\n\n(cherry picked from commit 907aebc5578ae09fa5c0e2f0784201295837e60b)",
  "id": "GHSA-23v5-2h3w-j9hf",
  "modified": "2026-11-20T06:32:05Z",
  "published": "2026-11-20T06:32:05Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99627"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/117e6ac89e730d647aeaf53b77420efece331f4d"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/374aba4bef461462a9640f8355ebff5d5021c459"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/cd38a2b45edf84324ee9572c09c279fd4ebec5fc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d1551515a3258b43cba60bd7f45bbdd1f4e9e60a"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.