---
id: CVE-2025-68230
title: |-
  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.…
summary: |-
  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.…
severity: none
published: '2025-12-16'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T13:10:00.187'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-68230'
references:
  - url: 'https://git.kernel.org/stable/c/a45d6359eefb41e08d374a3260b10bff5626823b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/eb6e7f520d6efa4d4ebf1671455abe4a681f7a05'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/eef72d856f978955e633c270abb1f7ec7b61c6d2'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00192
epssPercentile: 0.08214
ingestedAt: '2026-10-14T13:30:58.461Z'
---

## Overview

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)

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.