CVE-2024-27400

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

MEDIUM
5.5
CVSS Score
Published: May 13, 2024 at 10:26 AM UTC
Updated: August 5, 2026 at 12:04 PM UTC
2 products affected across 2 vendorsLinux KernelFedora

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.15.149v ≥ 6.7.45.15.149 ≤ v < 5.166.1.77 ≤ v < 6.1.916.6.16 ≤ v < 6.6.316.7.4 ≤ v < 6.86.7.4 ≤ v < 6.8.106.8 ≤ v < 6.8.106.8 ≤ v < 6.91cd2b612474c07b17a21e27f2eed8dff75cb50575.15.1496.1.776.6.166.7.46.9 rc16.9 rc26.9 rc36.9 rc46.9 rc56.9 rc677bcd4ab446fa35ad135b1c7404415ed9a12929694aeb4117343d072e3a35b9595bcbfc0058ee724d443fb67ca5ab04760449d21ddea66f6728e5b00e7a0ee45c653784edda5e36bae6ae3c75fd5e7a8
Vendor states this is fixed in 0c7ed3ed35eec9138b88d42217b5a6b9a62bda4d (fixed)
Vendor states this is fixed in 5c25b169f9a0b34ee410891a96bc9d7b9ed6f9be (fixed)
Vendor states this is fixed in 9a4f6e138720b6e9adf7b82a71d0292f3f276480 (fixed)
Vendor states this is fixed in d3a9331a6591e9df64791e076f6591f440af51c3 (fixed)
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.91 (unaffected)
Vendor states this is fixed in 6.6.31 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)
Vendor states this is fixed in 6.8.10 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)

References (6)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card