Answer in brief
CVE-2024-27400 records a Unknown severity vulnerability in drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-27400 records a Unknown severity vulnerability in drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d443fb67ca5ab04760449d21ddea66f6728e5b00 <5c25b169f9a0b34ee410891a96bc9d7b9ed6f9be || >=e7a0ee45c653784edda5e36bae6ae3c75fd5e7a8 <0c7ed3ed35eec9138b88d42217b5a6b9a62bda4d || >=94aeb4117343d072e3a35b9595bcbfc0058ee724 <9a4f6e138720b6e9adf7b82a71d0292f3f276480 || >=94aeb4117343d072e3a35b9595bcbfc0058ee724 <d3a9331a6591e9df64791e076f6591f440af51c3 || 77bcd4ab446fa35ad135b1c7404415ed9a129296 || 1cd2b612474c07b17a21e27f2eed8dff75cb5057 || >=6.1.77 <6.1.91 || >=6.6.16 <6.6.31 || >=5.15.149 <5.16 || >=6.7.4 <6.8 | 5c25b169f9a0b34ee410891a96bc9d7b9ed6f9be, 0c7ed3ed35eec9138b88d42217b5a6b9a62bda4d, 9a4f6e138720b6e9adf7b82a71d0292f3f276480, d3a9331a6591e9df64791e076f6591f440af51c3, 6.1.91, 6.6.31, 5.16, 6.8 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
May 13, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d443fb67ca5ab04760449d21ddea66f6728e5b00 <5c25b169f9a0b34ee410891a96bc9d7b9ed6f9be || >=e7a0ee45c653784edda5e36bae6ae3c75fd5e7a8 <0c7ed3ed35eec9138b88d42217b5a6b9a62bda4d || >=94aeb4117343d072e3a35b9595bcbfc0058ee724 <9a4f6e138720b6e9adf7b82a71d0292f3f276480 || >=94aeb4117343d072e3a35b9595bcbfc0058ee724 <d3a9331a6591e9df64791e076f6591f440af51c3 || 77bcd4ab446fa35ad135b1c7404415ed9a129296 || 1cd2b612474c07b17a21e27f2eed8dff75cb5057 || >=6.1.77 <6.1.91 || >=6.6.16 <6.6.31 || >=5.15.149 <5.16 || >=6.7.4 <6.8 | 5c25b169f9a0b34ee410891a96bc9d7b9ed6f9be, 0c7ed3ed35eec9138b88d42217b5a6b9a62bda4d, 9a4f6e138720b6e9adf7b82a71d0292f3f276480, d3a9331a6591e9df64791e076f6591f440af51c3, 6.1.91, 6.6.31, 5.16, 6.8 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
May 13, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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
Quoted source text, attributed separately from HOL analysis.