CVE-2024-27400: drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2
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
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux AMDGPU driver mishandles the order of memory-move notifications, leaving required old-location information unavailable. The supplied CVSS score is 7.8, reflecting potentially serious confidentiality, integrity, and availability consequences for an attacker who already has local low-privilege access.
Executive priority
Treat this as a high-priority kernel maintenance issue on confirmed AMDGPU systems, especially shared or multi-user hosts. It is not an internet-wide emergency because exploitation requires local access and active exploitation is not established. Complete vendor-guided updates promptly within the normal urgent patch cycle.
Technical view
In amdgpu_ttm_move(), the move notification occurred after the buffer move, when the old location was no longer available. This also produced incorrect ordering for DMA-buf and virtual-memory notifications. The resolution restores notification before movement, revises eviction-statistic handling, and adds a missing NULL check.
Likely exposure
Exposure is limited to Linux systems using the AMDGPU driver and an affected kernel build. The supplied version data includes ambiguous entries, including "0", so administrators should confirm exposure using distribution advisories, package changelogs, or inclusion of the cited stable-kernel fixes rather than version strings alone.
Exploitation context
The CVSS vector requires local access, low privileges, low complexity, and no user interaction. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. It is not described as remotely exploitable.
Researcher notes
No CWE or precise exploitation primitive is supplied. The available description establishes notification-order, statistics, and NULL-check corrections but does not explain how an attacker reaches the condition. The affected-version representation is internally difficult to interpret; validate using vendor packages and the referenced kernel commits.
Mitigation direction
Inventory Linux systems using AMDGPU hardware or the AMDGPU kernel driver.
Install a vendor-supported kernel containing the applicable stable fix.
Prioritize multi-user workstations and shared GPU compute systems with untrusted local users.
Reboot where required and confirm the updated kernel is active.
Consult distribution guidance where package-to-upstream version mapping is unclear.
Validation and detection
Record the running kernel release and package build on every AMDGPU system.
Confirm the installed package changelog references this CVE or a cited stable fix.
Verify whether the AMDGPU driver is active on each potentially affected host.
Check for pending reboots that leave an older vulnerable kernel running.
After updating, test GPU workloads and review kernel logs for regressions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-27400 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.