drm/amdkfd: fix 32-bit overflow in CWSR total size calculation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| 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/amdkfd: fix 32-bit overflow in CWSR total size calculation
total_cwsr_size was computed in 32-bit before being used as a BO/SVM allocation size. With large ctx_save_restore_area_size and debug_memory_size multiplied by the XCC count, the product can wrap, yielding an undersized CWSR save area that firmware later overruns.
Promote total_cwsr_size to u64 and use check_add_overflow()/ check_mul_overflow() in both kfd_queue_acquire_buffers() and kfd_queue_release_buffers().
(cherry picked from commit 319f7e13423ae3f486b9aea82f9ad2d6af0ee608)
From the CVE record · Linux
A 32-bit overflow in the Linux kernel's drm/amdkfd CWSR size calculation can produce an undersized save-area allocation. When large context save/restore and debug-memory sizes are multiplied by the XCC count, firmware can overrun that allocation. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with drm/amdkfd should check their kernel versions; affected versions were not provided.