All reports
Medium

kernel: drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2024-27400

Probability of exploitation in the next 30 days: 0.24%

FIRST EPSS · 2026-11-18

Description

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

A vulnerability was found in the AMDGPU driver, theamdgpu_ttm_move() function, within the Linux kernel. This issue, resolved in version updates, involved a flaw in handling memory moves for GPU resources, which led to undefined behavior and potential system instability.