Answer in brief
CVE-2026-93139 records a Unknown severity vulnerability in drm/amdgpu/mes: Fix hung_queue_db_array loop limit for multi-XCC. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a132fc9bc2f8b394a2f75947a0e1f5c22482a94c <7ff668cfc3960ed5b944ac35129f18a15ea08b74 || >=a132fc9bc2f8b394a2f75947a0e1f5c22482a94c <2c256086a363f01f9840a57949506eccf5c990a6 | 7ff668cfc3960ed5b944ac35129f18a15ea08b74, 2c256086a363f01f9840a57949506eccf5c990a6 |
| Linux/Linuxgeneric | 7.2 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.