Vulnerability-Lookup

GHSA-HF6P-44H5-HP6X

Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 15:30

Details

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: clamp the isolation index for rings outside a partition

adev->isolation[] has one slot per partition, but a ring that is not assigned to one keeps AMDGPU_XCP_NO_PARTITION, which is ~0, so indexing the array with it is out of bounds. SDMA submissions hit this on both the isolation enforcement and the VM flush path and trip UBSAN.

Fall back to the first slot the way the cleaner shader path already does, and stop taking the address before the ring type check that makes it relevant.

Severity

7.8 (High)


                  
                    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-89814"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-16T11:16:46Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: clamp the isolation index for rings outside a partition\n\nadev-\u003eisolation[] has one slot per partition, but a ring that is not\nassigned to one keeps AMDGPU_XCP_NO_PARTITION, which is ~0, so indexing\nthe array with it is out of bounds. SDMA submissions hit this on both\nthe isolation enforcement and the VM flush path and trip UBSAN.\n\nFall back to the first slot the way the cleaner shader path already\ndoes, and stop taking the address before the ring type check that makes\nit relevant.",
  "id": "GHSA-hf6p-44h5-hp6x",
  "modified": "2026-09-16T15:30:58Z",
  "published": "2026-09-16T12:30:37Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89814"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0bfb938182d1313e5cac32ae38dbaaa4eabe4af4"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/964de255497ffd7cb8a86e405b8ac6d927e7e177"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b30900566642ceb2c9e12b56c2afec28d0fd91a0"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-89814 (GCVE-0-2026-89814)

Vulnerability from cvelistv5 – Published: 2026-09-16 10:30 – Updated: 2026-10-19 08:53

Title

drm/amdgpu: clamp the isolation index for rings outside a partition

Summary

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: clamp the isolation index for rings outside a partition adev->isolation[] has one slot per partition, but a ring that is not assigned to one keeps AMDGPU_XCP_NO_PARTITION, which is ~0, so indexing the array with it is out of bounds. SDMA submissions hit this on both the isolation enforcement and the VM flush path and trip UBSAN. Fall back to the first slot the way the cleaner shader path already does, and stop taking the address before the ring type check that makes it relevant.

Severity

7.8 (High)


                        
                          CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 6639 records in the last 180 days details

References

3 references

URL	Tags
https://git.kernel.org/stable/c/964de255497ffd7cb…
https://git.kernel.org/stable/c/0bfb938182d1313e5…
https://git.kernel.org/stable/c/b30900566642ceb2c…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: bd22e44ad415ac22e3a4f9a983d2a085f6cb4427 , < 964de255497ffd7cb8a86e405b8ac6d927e7e177 (git) Affected: bd22e44ad415ac22e3a4f9a983d2a085f6cb4427 , < 0bfb938182d1313e5cac32ae38dbaaa4eabe4af4 (git) Affected: bd22e44ad415ac22e3a4f9a983d2a085f6cb4427 , < b30900566642ceb2c9e12b56c2afec28d0fd91a0 (git) Affected: 4277dc1942a8979abe1ef2b55069f42497f885c0 (git) Affected: 6.14.9 , < 6.15 (semver)
Linux	Linux	Affected: 6.15 Unaffected: 0 , < 6.15 (semver) Unaffected: 6.18.51 , ≤ 6.18.* (semver) Unaffected: 7.2.5 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/amd/amdgpu/amdgpu_device.c",
            "drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "964de255497ffd7cb8a86e405b8ac6d927e7e177",
              "status": "affected",
              "version": "bd22e44ad415ac22e3a4f9a983d2a085f6cb4427",
              "versionType": "git"
            },
            {
              "lessThan": "0bfb938182d1313e5cac32ae38dbaaa4eabe4af4",
              "status": "affected",
              "version": "bd22e44ad415ac22e3a4f9a983d2a085f6cb4427",
              "versionType": "git"
            },
            {
              "lessThan": "b30900566642ceb2c9e12b56c2afec28d0fd91a0",
              "status": "affected",
              "version": "bd22e44ad415ac22e3a4f9a983d2a085f6cb4427",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "4277dc1942a8979abe1ef2b55069f42497f885c0",
              "versionType": "git"
            },
            {
              "lessThan": "6.15",
              "status": "affected",
              "version": "6.14.9",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/amd/amdgpu/amdgpu_device.c",
            "drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.15"
            },
            {
              "lessThan": "6.15",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.51",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.51",
                  "versionStartIncluding": "6.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.5",
                  "versionStartIncluding": "6.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "6.14.9",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: clamp the isolation index for rings outside a partition\n\nadev-\u003eisolation[] has one slot per partition, but a ring that is not\nassigned to one keeps AMDGPU_XCP_NO_PARTITION, which is ~0, so indexing\nthe array with it is out of bounds. SDMA submissions hit this on both\nthe isolation enforcement and the VM flush path and trip UBSAN.\n\nFall back to the first slot the way the cleaner shader path already\ndoes, and stop taking the address before the ring type check that makes\nit relevant."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The OOB is in amdgpu_device_enforce_isolation() and amdgpu_vm_flush(), reached only via local DRM ioctls on /dev/dri/renderD* (AMDGPU_CS and GEM_VA/VM updates that schedule SDMA jobs through amdgpu_job_prepare_job/amdgpu_ib_schedule). There is no network, adjacent-radio, or physical packet path.\nAC:L - Unassigned rings already have xcp_id=AMDGPU_XCP_NO_PARTITION (~0), so indexing adev-\u003eisolation[MAX_XCP] is deterministic on each SDMA or GFX/compute job. The attacker only needs to submit ordinary command buffers or VA maps; no race or uninfluenced layout is required.\nPR:L - AMDGPU_CS, GEM_VA, and related ioctls are DRM_AUTH|DRM_RENDER_ALLOW with no capability check, so any unprivileged local user with render-node access (render/video group, Android GPU clients, multi-tenant cloud GPU VMs) can reach the scheduler without init-namespace root.\nUI:N - The attacker opens the render node and submits their own command buffers or GEM_VA maps; no separate victim action such as mounting a filesystem, opening a file, or interacting with another user\u0027s GPU context is required.\nS:U - The isolation[] out-of-bounds access corrupts host kernel memory inside the amdgpu driver. It does not cross a VM, IOMMU/DMA, or guest-to-host boundary into a different security authority.\nC:H - Indexing isolation[ring-\u003excp_id] with ~0 is an unbounded kernel out-of-bounds access. amdgpu_vm_flush reads isolation-\u003espearhead and enforce_isolation reads spearhead/owner/sync fence objects, which can disclose kernel pointers; CNA guidance scores OOB reads High unless limited to a few bytes.\nI:H - For GFX/compute rings, amdgpu_device_enforce_isolation writes isolation-\u003espearhead, owner, and amdgpu_sync hash tables at the OOB address and dma_fence_put()s a wild fence pointer, which is an out-of-bounds write and UAF/control-flow primitive scored High.\nA:H - The ~0 index yields a wildly invalid pointer whose dereference oopses the host, and UBSAN array-index-out-of-bounds aborts under CONFIG_UBSAN_TRAP or panic_on_warn. Either outcome is a kernel crash that fully denies GPU/host availability."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:53:08.487Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/964de255497ffd7cb8a86e405b8ac6d927e7e177"
        },
        {
          "url": "https://git.kernel.org/stable/c/0bfb938182d1313e5cac32ae38dbaaa4eabe4af4"
        },
        {
          "url": "https://git.kernel.org/stable/c/b30900566642ceb2c9e12b56c2afec28d0fd91a0"
        }
      ],
      "title": "drm/amdgpu: clamp the isolation index for rings outside a partition",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89814",
    "datePublished": "2026-09-16T10:30:47.167Z",
    "dateReserved": "2026-09-11T19:38:34.768Z",
    "dateUpdated": "2026-10-19T08:53:08.487Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

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

Order 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.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.

Action not permitted