CVE-2024-27400
drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2
| Assigner | Linux |
| Reserved | 2024-02-25 |
| Published | 2024-05-13 |
| Updated | 2024-09-11 |
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2 This reverts drm/amdgpu: fix ftrace event amdgpu_bo_move always move on same heap. The basic problem here is that after the move the old location is simply not available any more. Some fixes were suggested, but essentially we should call the move notification before actually moving things because only this way we have the correct order for DMA-buf and VM move notifications as well. Also rework the statistic handling so that we don't update the eviction counter before the move. v2: add missing NULL check
https://git.kernel.org/stable/c/5c25b169f9a0b34ee410891a96bc9d7b9ed6f9be
https://git.kernel.org/stable/c/0c7ed3ed35eec9138b88d42217b5a6b9a62bda4d
https://git.kernel.org/stable/c/9a4f6e138720b6e9adf7b82a71d0292f3f276480
https://git.kernel.org/stable/c/d3a9331a6591e9df64791e076f6591f440af51c3
