drm/amdgpu: add upper bound check on user inputs in signal ioctl
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 |
|
|
6.18.196.19.97.0In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: add upper bound check on user inputs in signal ioctl
Huge input values in amdgpu_userq_signal_ioctl can lead to a OOM and could be exploited.
So check these input value against AMDGPU_USERQ_MAX_HANDLES which is big enough value for genuine use cases and could potentially avoid OOM.
(cherry picked from commit be267e15f99bc97cbe202cd556717797cdcf79a5)
From the CVE record · Linux
The Linux kernel's amdgpu signal ioctl lacks an upper-bound check on user-supplied values. A local user able to invoke the ioctl could supply huge values and cause an out-of-memory condition.
Teams running Linux kernels with the amdgpu driver should check their deployments; affected versions were not specified.