CVE-2024-27400: Vulnerability in Linux Linux
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
AI Analysis
Technical Summary
CVE-2024-27400 is a vulnerability identified in the Linux kernel specifically within the AMDGPU driver component, which handles graphics processing for AMD GPUs. The issue centers around the function amdgpu_ttm_move(), responsible for managing memory moves related to the Translation Table Maps (TTM) used by the AMDGPU driver. The vulnerability arises from an incorrect order of operations during the move process. Specifically, the move notification, which informs other kernel components about the relocation of graphics memory buffers, was being called after the actual move operation. This sequence caused inconsistencies because the old memory location was no longer available when notifications were sent, potentially leading to stale references or race conditions. The fix involves calling the move notification before the actual move, ensuring that dependent components like DMA-buf and virtual memory (VM) move notifications receive updates in the correct order. Additionally, the patch reworks statistic handling to prevent premature updates to the eviction counter before the move completes and adds a missing NULL pointer check to improve stability. This vulnerability affects multiple recent Linux kernel versions as indicated by the commit hashes listed. Although no known exploits are reported in the wild, the flaw could theoretically lead to memory corruption or instability in systems using AMD GPUs under Linux, potentially impacting graphics performance or causing kernel crashes.
Potential Impact
For European organizations, the impact of CVE-2024-27400 depends largely on their reliance on Linux systems with AMD GPU hardware, particularly in environments where graphics performance and stability are critical, such as media production, scientific computing, or virtualization platforms. Exploitation could lead to denial of service through kernel crashes or memory corruption, affecting availability of services. In multi-tenant or cloud environments, improper handling of GPU memory moves could potentially be leveraged for privilege escalation or data leakage between processes, although no direct evidence of such exploitation exists currently. Organizations running Linux-based desktops, servers, or embedded systems with AMD GPUs should be aware of the risk of system instability or degraded performance if unpatched. Given the widespread use of Linux in European public sector, research institutions, and enterprises, the vulnerability could have a broad impact if exploited, especially in countries with high adoption of open-source infrastructure.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should prioritize updating their Linux kernels to versions that include the patch for CVE-2024-27400 as soon as vendor updates become available. Since the vulnerability is in the AMDGPU driver, systems without AMD GPUs or those using alternative drivers are not affected. Organizations should audit their environments to identify affected systems by checking for AMD GPU presence and kernel versions. For environments where immediate patching is not feasible, consider isolating affected systems or limiting access to reduce risk exposure. Monitoring kernel logs for unusual GPU-related errors or crashes can provide early detection of exploitation attempts. Additionally, organizations should ensure that their Linux distributions are subscribed to security update channels and that automated patch management processes are in place to reduce patch latency. Collaboration with hardware vendors and Linux distribution maintainers can help accelerate deployment of fixes.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Denmark, Belgium, Italy, Spain
CVE-2024-27400: Vulnerability in Linux Linux
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
AI-Powered Analysis
Technical Analysis
CVE-2024-27400 is a vulnerability identified in the Linux kernel specifically within the AMDGPU driver component, which handles graphics processing for AMD GPUs. The issue centers around the function amdgpu_ttm_move(), responsible for managing memory moves related to the Translation Table Maps (TTM) used by the AMDGPU driver. The vulnerability arises from an incorrect order of operations during the move process. Specifically, the move notification, which informs other kernel components about the relocation of graphics memory buffers, was being called after the actual move operation. This sequence caused inconsistencies because the old memory location was no longer available when notifications were sent, potentially leading to stale references or race conditions. The fix involves calling the move notification before the actual move, ensuring that dependent components like DMA-buf and virtual memory (VM) move notifications receive updates in the correct order. Additionally, the patch reworks statistic handling to prevent premature updates to the eviction counter before the move completes and adds a missing NULL pointer check to improve stability. This vulnerability affects multiple recent Linux kernel versions as indicated by the commit hashes listed. Although no known exploits are reported in the wild, the flaw could theoretically lead to memory corruption or instability in systems using AMD GPUs under Linux, potentially impacting graphics performance or causing kernel crashes.
Potential Impact
For European organizations, the impact of CVE-2024-27400 depends largely on their reliance on Linux systems with AMD GPU hardware, particularly in environments where graphics performance and stability are critical, such as media production, scientific computing, or virtualization platforms. Exploitation could lead to denial of service through kernel crashes or memory corruption, affecting availability of services. In multi-tenant or cloud environments, improper handling of GPU memory moves could potentially be leveraged for privilege escalation or data leakage between processes, although no direct evidence of such exploitation exists currently. Organizations running Linux-based desktops, servers, or embedded systems with AMD GPUs should be aware of the risk of system instability or degraded performance if unpatched. Given the widespread use of Linux in European public sector, research institutions, and enterprises, the vulnerability could have a broad impact if exploited, especially in countries with high adoption of open-source infrastructure.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should prioritize updating their Linux kernels to versions that include the patch for CVE-2024-27400 as soon as vendor updates become available. Since the vulnerability is in the AMDGPU driver, systems without AMD GPUs or those using alternative drivers are not affected. Organizations should audit their environments to identify affected systems by checking for AMD GPU presence and kernel versions. For environments where immediate patching is not feasible, consider isolating affected systems or limiting access to reduce risk exposure. Monitoring kernel logs for unusual GPU-related errors or crashes can provide early detection of exploitation attempts. Additionally, organizations should ensure that their Linux distributions are subscribed to security update channels and that automated patch management processes are in place to reduce patch latency. Collaboration with hardware vendors and Linux distribution maintainers can help accelerate deployment of fixes.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-02-25T13:47:42.681Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9821c4522896dcbddbee
Added to database: 5/21/2025, 9:08:49 AM
Last enriched: 6/28/2025, 3:10:22 AM
Last updated: 7/31/2025, 10:21:28 AM
Views: 13
Related Threats
CVE-2025-9091: Hard-coded Credentials in Tenda AC20
LowCVE-2025-9090: Command Injection in Tenda AC20
MediumCVE-2025-9092: CWE-400 Uncontrolled Resource Consumption in Legion of the Bouncy Castle Inc. Bouncy Castle for Java - BC-FJA 2.1.0
LowCVE-2025-9089: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-9088: Stack-based Buffer Overflow in Tenda AC20
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.