VulnerabilityPublished 26 Oct 2026

CVE-2026-99090: Linux kernel · drm/amdgpu: serialize vblank counter reads against GPU reset

Source GCVE Database

Authoritative record:CVE-2026-99090· Low

Not known to be exploited · fixed in f4a0a1ce147d1a6e428d7cb5e3b99fd695139fc7 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 16:31 UTC

Severity

Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in f4a0a1ce147d1a6e428d7cb5e3b99fd695139fc7, 037796d9ca1da97978deaefd88ca5649f6cb69f5, 11b6193c8841a052b7907006ffb1e02468b1448e +6

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-3hrf-vpmj-gj4m

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected <6.6.160 <6.12.113 <6.18.57 <7.2.11	Fixed in f4a0a1ce147d1a6e428d7cb5e3b99fd695139fc7 037796d9ca1da97978deaefd88ca5649f6cb69f5 11b6193c8841a052b7907006ffb1e02468b1448e 8d6f773d7479034a574ecc3b585bcd07d46b4824 7.2.11 6.18.57 6.12.113 6.6.160 1a6023edfbb5673f55fab6348f135fb3b1428ea5

AI-suggested

A fix has been implemented in the Linux kernel AMDGPU driver that serializes vblank counter reads against GPU reset by acquiring the reset semaphore for reading or returning a cached software count during reset. Users should update to the fixed kernel version containing commit 51a4359f7431a4be5e42803c8bdaf7e0e5be2934. No additional mitigation is required.

Description

A vulnerability in the Linux kernel's AMDGPU driver involves improper serialization of vblank counter reads against GPU reset operations. During GPU recovery, hardware register reads can occur while a reset semaphore is held for writing, causing lock dependency assertion failures and kernel taint warnings. The fix involves acquiring the reset semaphore for reading before hardware access or returning a cached software count if reset is in progress, preventing unsafe hardware access during reset.

References

Community reviews

Loading reviews…