CVE-2026-93139
Severity not reportedData quality: partial.
Some fields were not provided by the source.
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 A…
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.
CVSS
—
Awaiting analysis by NVD
Timeline (UTC)
Published: 2026-09-17 17:18
Modified: 2026-10-19 10:17
NVD status: Received
Last synced 2 days ago
Verified against the source API 2026-10-27 06:54 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
Not reported by the source (unknown — not "none").
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://git.kernel.org/stable/c/2c256086a363f01f9840a57949506eccf5c990a6 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/7ff668cfc3960ed5b944ac35129f18a15ea08b74 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Data sources
NVD CVE API 2.0 — fetched 2026-10-27 06:54 UTC · record ↗