# CVE-2026-93139: drm/amdgpu/mes: Fix hung_queue_db_array loop limit for multi-XCC

> A null pointer dereference in the AMDGPU kernel driver can cause a system crash on multi-XCC GPUs due to uninitialized array entries.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-h628-62x6-4jjj, UBUNTU-CVE-2026-93139

## What is CVE-2026-93139?

CVE-2026-93139 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

drm/amdgpu/mes: Fix hung_queue_db_array loop limit for multi-XCC

The loop iterated only AMDGPU_MAX_MES_PIPES times, leaving entries
uninitialized for multi-XCC GPUs. This causes null pointer dereferences
when accessing arrays indexed by XCC ID >= 2. Extend the loop to cover
all XCCs (AMDGPU_MAX_MES_PIPES * num_xcc), matching other per-XCC
arrays.

## Which versions are affected by CVE-2026-93139?


## How do I fix CVE-2026-93139?

Apply the vendor's patch.

## Is CVE-2026-93139 being exploited?

There is no known exploitation of CVE-2026-93139 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93139 and fix it if it is affected.

What it is: CVE-2026-93139 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93139 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93139/ (Markdown: https://insights.sbomify.com/CVE-2026-93139/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93139
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93139
- OSV: https://osv.dev/vulnerability/CVE-2026-93139

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93139/
Summaries are generated and may contain mistakes; the official description above is the record.