Answer in brief
CVE-2025-68230 records a Unknown severity vulnerability in drm/amdgpu: fix gpu page fault after hibernation on PF passthrough. 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 | >=955220b04d42c41050158fec0f53957f320b96f9 <f0ee42f47cc1b0a95d2d22ba352ff89fc0cd13d4 || >=955220b04d42c41050158fec0f53957f320b96f9 <a45d6359eefb41e08d374a3260b10bff5626823b || >=955220b04d42c41050158fec0f53957f320b96f9 <eef72d856f978955e633c270abb1f7ec7b61c6d2 || >=955220b04d42c41050158fec0f53957f320b96f9 <eb6e7f520d6efa4d4ebf1671455abe4a681f7a05 | f0ee42f47cc1b0a95d2d22ba352ff89fc0cd13d4, a45d6359eefb41e08d374a3260b10bff5626823b, eef72d856f978955e633c270abb1f7ec7b61c6d2, eb6e7f520d6efa4d4ebf1671455abe4a681f7a05 |
| Linux/Linuxgeneric | 6.5 | Not reported |
Published upstream
Dec 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix gpu page fault after hibernation on PF passthrough On PF passthrough environment, after hibernate and then resume, coralgemm will cause gpu page fault. Mode1 reset happens during hibernate, but partition mode is not restored on resume, register mmCP_HYP_XCP_CTL and mmCP_PSP_XCP_CTL is not right after resume. When CP access the MQD BO, wrong stride size is used, this will cause out of bound access on the MQD BO, resulting page fault. The fix is to ensure gfx_v9_4_3_switch_compute_partition() is called when resume from a hibernation. KFD resume is called separately during a reset recovery or resume from suspend sequence. Hence it's not required to be called as part of partition switch. (cherry picked from commit 5d1b32cfe4a676fe552416cb5ae847b215463a1a)
Quoted source text, attributed separately from HOL analysis.