CVE-2026-99090: Linux Vulnerability

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)

Metrics

EPSS Probability

0.16%

5.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= d38ceaf99ed015f2a0b9af3499791bd3a3daae21, < 037796d9ca1da97978deaefd88ca5649f6cb69f5; >= d38ceaf99ed015f2a0b9af3499791bd3a3daae21, < 11b6193c8841a052b7907006ffb1e02468b1448e; >= d38ceaf99ed015f2a0b9af3499791bd3a3daae21, < 8d6f773d7479034a574ecc3b585bcd07d46b4824; >= d38ceaf99ed015f2a0b9af3499791bd3a3daae21, < f4a0a1ce147d1a6e428d7cb5e3b99fd695139fc7; >= d38ceaf99ed015f2a0b9af3499791bd3a3daae21, < 1a6023edfbb5673f55fab6348f135fb3b1428ea5
Linux	Linux	4.2

References

Timeline

Published: Oct 26, 2026
Last Modified: Oct 27, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-99090?

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)

How severe is CVE-2026-99090?

Severity scoring for CVE-2026-99090 is pending analysis. The EPSS model estimates a 0.16% probability of exploitation in the next 30 days.

How do I fix CVE-2026-99090?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →