CVE-2025-68230

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)

Package Linux Kernel
Published 2025-12-16
Last modified 2026-04-15
Patch available
Yes

Affected versions

Linux kernel versions 6.5 and later are affected. Fixed in 6.12.60, 6.17.10, 6.18 and their respective stable series.

Affected from
≥ 6.5
Fixed in
✓ 6.12.60 6.12.x ✓ 6.17.10 6.17.x ✓ 6.18

References

The following references provide additional information about CVE-2025-68230 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Frequently asked questions

  • What is CVE-2025-68230?

    CVE-2025-68230 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.5 onward and has been patched in 6.12.60, 6.17.10 and 6.18. CVE-2025-68230 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2025-68230?

    Yes — CVE-2025-68230 has been patched. Fixed versions include 6.12.60, 6.17.10 and 6.18. If you are running Linux kernel 6.5 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2025-68230 actively exploited?

    No — CVE-2025-68230 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.