CVE-2026-99090

drm/amdgpu: serialize vblank counter reads against GPU reset

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: serialize vblank counter reads against GPU reset The vblank counter callback reads display registers and scanout position without holding reset_domain->sem. During GPU recovery, display commit work can call the callback while reset owns the semaphore for writing. The hardware access then triggers the lockdep_assert_held() in amdgpu_device_skip_hw_access() and sets TAINT_WARN when lockdep is enabled. Try to acquire the reset semaphore for reading before accessing the hardware, and hold it across the counter and scanout-position reads. If reset is already in progress, return DRM's cached software vblank count instead. This avoids blocking behind reset and avoids accessing display hardware while it is being reset. The cached count is less accurate than the hardware count, but is used only when reset prevents a safe hardware read. This addresses the reset-time warning from this vblank path; it does not suppress or fix unrelated lockdep warnings. (cherry picked from commit 51a4359f7431a4be5e42803c8bdaf7e0e5be2934)

Key facts

Published
26 Oct 2026
Last changed
27 Oct 2026
Assigned by
Linux
EPSS
0.164% likely to be exploited in the next 30 days, higher than 5.632% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 up to but excluding 037796d9ca1da97978deaefd88ca5649f6cb69f5 (affected)
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 up to but excluding 11b6193c8841a052b7907006ffb1e02468b1448e (affected)
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 up to but excluding 8d6f773d7479034a574ecc3b585bcd07d46b4824 (affected)
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 up to but excluding f4a0a1ce147d1a6e428d7cb5e3b99fd695139fc7 (affected)
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 up to but excluding 1a6023edfbb5673f55fab6348f135fb3b1428ea5 (affected)
LinuxLinux
  • Default status: affected
  • 4.2 (affected)
  • 0 up to but excluding 4.2 (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 26 Oct 2026 Published

References