CVE-2025-68793 Linux CVE debrief

Who should care

Linux kernel developers, AMDGPU driver maintainers, and users of systems with AMD GPUs should be aware of this vulnerability and take steps to mitigate it. This includes reviewing and updating AMDGPU driver configurations, monitoring system logs for suspicious GPU activity, and applying patches from the Linux kernel stable branch.

Technical summary

The vulnerability occurs in the AMDGPU driver's GPU recovery function, where a race condition between the scheduler timeout callback and the TDR work queue can lead to accessing a freed job, resulting in a use-after-free error. The fix involves caching the job's pasid early to avoid the use-after-free. This vulnerability can be triggered during GPU recovery, and it requires the AMDGPU driver to be updated to a version that includes the fix.

Defensive priority

High

Recommended defensive actions

• Apply the patch from the Linux kernel stable branch
• Review and update AMDGPU driver configurations
• Monitor system logs for suspicious GPU activity
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The vulnerability was resolved in the Linux kernel. Official CVE and NVD records provide details. Limited information is available about the CVE's impact and affected scope. The vulnerability was found in the Linux kernel's AMDGPU driver, which is used in systems with AMD GPUs. The vulnerability occurs due to a race condition between the scheduler timeout callback and the TDR work queue during GPU recovery. This can lead to accessing a freed job and result in a use-after-free error. To verify, defenders should review the official CVE and NVD records, check system logs for suspicious GPU activity, and ensure that the AMDGPU driver is up-to-date.

Official resources