Answer in brief
CVE-2025-37854 records a Unknown severity vulnerability in drm/amdkfd: Fix mode1 reset crash issue. 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 | >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <57c9dabda80ac167de8cd71231baae37cc2f442d || >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <89af6b39f028c130d4362f57042927f005423e6a || >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <ffd37d7d44d7e0b6e769d4fe6590e327f8cc3951 || >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <6f30a847432cae84c7428e9b684b3e3fa49b2391 || >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <9c4bcdf4068aae3e17e31c144300be405cfa03ff || >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <f0b4440cdc1807bb6ec3dce0d6de81170803569b | 57c9dabda80ac167de8cd71231baae37cc2f442d, 89af6b39f028c130d4362f57042927f005423e6a, ffd37d7d44d7e0b6e769d4fe6590e327f8cc3951, 6f30a847432cae84c7428e9b684b3e3fa49b2391, 9c4bcdf4068aae3e17e31c144300be405cfa03ff, f0b4440cdc1807bb6ec3dce0d6de81170803569b |
| Linux/Linuxgeneric | 5.18 | Not reported |
Published upstream
May 9, 2025
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/amdkfd: Fix mode1 reset crash issue If HW scheduler hangs and mode1 reset is used to recover GPU, KFD signal user space to abort the processes. After process abort exit, user queues still use the GPU to access system memory before h/w is reset while KFD cleanup worker free system memory and free VRAM. There is use-after-free race bug that KFD allocate and reuse the freed system memory, and user queue write to the same system memory to corrupt the data structure and cause driver crash. To fix this race, KFD cleanup worker terminate user queues, then flush reset_domain wq to wait for any GPU ongoing reset complete, and then free outstanding BOs.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-37854 records a Unknown severity vulnerability in drm/amdkfd: Fix mode1 reset crash issue. 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 | >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <57c9dabda80ac167de8cd71231baae37cc2f442d || >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <89af6b39f028c130d4362f57042927f005423e6a || >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <ffd37d7d44d7e0b6e769d4fe6590e327f8cc3951 || >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <6f30a847432cae84c7428e9b684b3e3fa49b2391 || >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <9c4bcdf4068aae3e17e31c144300be405cfa03ff || >=a4c63cafa58b4bd9e15511bab77a4752b93d3aa0 <f0b4440cdc1807bb6ec3dce0d6de81170803569b | 57c9dabda80ac167de8cd71231baae37cc2f442d, 89af6b39f028c130d4362f57042927f005423e6a, ffd37d7d44d7e0b6e769d4fe6590e327f8cc3951, 6f30a847432cae84c7428e9b684b3e3fa49b2391, 9c4bcdf4068aae3e17e31c144300be405cfa03ff, f0b4440cdc1807bb6ec3dce0d6de81170803569b |
| Linux/Linuxgeneric | 5.18 | Not reported |
Published upstream
May 9, 2025
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/amdkfd: Fix mode1 reset crash issue If HW scheduler hangs and mode1 reset is used to recover GPU, KFD signal user space to abort the processes. After process abort exit, user queues still use the GPU to access system memory before h/w is reset while KFD cleanup worker free system memory and free VRAM. There is use-after-free race bug that KFD allocate and reuse the freed system memory, and user queue write to the same system memory to corrupt the data structure and cause driver crash. To fix this race, KFD cleanup worker terminate user queues, then flush reset_domain wq to wait for any GPU ongoing reset complete, and then free outstanding BOs.
Quoted source text, attributed separately from HOL analysis.