drm/amdgpu/mes: Fix hung_queue_db_array loop limit for multi-XCC
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In the Linux kernel’s amdgpu MES code, a loop leaves entries uninitialized on multi-XCC GPUs, causing null pointer dereferences when arrays are indexed by XCC ID 2 or higher. The input does not describe how an attacker could trigger this, or whether authentication or user interaction is required.
Engineers running Linux on systems with multi-XCC GPUs should check their kernel versions; affected versions are not specified.