drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ dfd57dbf44ddc70c90c76f83b2deb46e5dd40ce3 · < a2baf12eec41f246689e6a3f8619af1200031576| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring
JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences.
(cherry picked from commit 4d7d774f100efb5089c86a1fb8c5bf47c63fc9ef)
From the CVE record · Linux
The Linux kernel's AMDGPU JPEG v3.0 ring does not support 64-bit user fence writes, but it did not reject command submissions with user fences. Such submissions could reach a ring that cannot support them; the input does not specify the resulting impact or the access conditions required.
Engineers running Linux kernels with the AMDGPU JPEG v3.0 ring should check whether their kernel includes the fix; affected versions are not specified.