drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0b988ca1c7c4c73983b4ea96ef7c2af2263c87eb · < 6c6064cbe58b43533e3451ad6a8ba9736c109ac3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag
Otherwise after the GTT bo is released, the GTT and gart space is freed but amdgpu_ttm_backend_unbind will not clear the gart page table entry and leave valid mapping entry pointing to the stale system page. Then if GPU access the gart address mistakely, it will read undefined value instead page fault, harder to debug and reproduce the real issue.
From the CVE record · Linux
The Linux kernel’s amdgpu driver can leave a valid GART page-table entry pointing to a stale system page after a GTT buffer object is released. If the GPU mistakenly accesses that address, it reads an undefined value instead of triggering a page fault. The input does not describe an attacker path, authentication requirements, or user interaction.
Teams running Linux kernels with the amdgpu driver should check their exposure; affected versions are not specified.