drm/amdgpu: avoid force-completing uninitialized UVD rings
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: avoid force-completing uninitialized UVD rings
uvd_v7_0_sw_init() does not initialize the UVD decode ring for an SR-IOV VF. However, amdgpu_uvd_resume() unconditionally force-completes the decode ring when restoring its fence sequence.
Skip fence completion when the fence driver is not initialized.
From the CVE record · Linux
The Linux kernel’s amdgpu driver can force-complete an uninitialized UVD decode ring when restoring its fence sequence on an SR-IOV virtual function. The input does not specify an attacker action, resulting impact, access requirements, or user interaction.
Operators running the Linux kernel with amdgpu SR-IOV virtual functions should check their affected versions against the vendor advisory; no versions are specified here.