drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
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.176.19.77.0In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
Userspace can either deliberately pass in the too small num_fences, or the required number can legitimately grow between the two calls to the userq wait ioctl. In both cases we do not want the emit the kernel warning backtrace since nothing is wrong with the kernel and userspace will simply get an errno reported back. So lets simply drop the WARN_ONs.
(cherry picked from commit 2c333ea579de6cc20ea7bc50e9595ef72863e65c)
From the CVE record · Linux
The Linux kernel’s amdgpu userq wait ioctl can emit a kernel warning backtrace when userspace supplies too small a num_fences value or the required number grows between calls. A local userspace caller can deliberately trigger the warning; the ioctl otherwise reports an error to userspace.
Teams running Linux kernels with the affected amdgpu userq code should check their kernel versions against the vendor advisory.