CVE-2024-27400: drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-05-14 · updated 2026-08-04

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

Affected products

Fedoraproject Fedora: 39, 40
Linux kernel: from 5.15.149 before 5.16; from 6.1.77 before 6.1.91; from 6.6.16 before 6.6.31; from 6.7.4 before 6.8.10; 6.9-rc1, 6.9-rc2, 6.9-rc3, 6.9-rc4, 6.9-rc5, 6.9-rc6 — fixed in 5.16, 6.1.91, 6.6.31, 6.8.10

How to fix

Upgrade to a fixed version: Linux kernel 5.16, 6.1.91, 6.6.31, 6.8.10. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-27400 or the next vulnerability affects your stack