CVE-2026-98654: drm/amd/display: Atomize IRQ register read/modify/write ops
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernel drm/amd/displayto a version that resolves this vulnerability.Patch 70de0a0216583a53c946155f8c8adedfdca6b4e7
Event History
Frequently Asked Questions
What systems are exposed to this race condition?
Systems using the Linux kernel AMD display driver and relying on the output timing generator's VUPDATE_NO_LOCK interrupt for vblank handling are relevant. The issue concerns the OTG_GLOBAL_SYNC_STATUS register handling in that driver path.
What condition triggers the problem?
The race requires the VUPDATE_NO_LOCK hardware IRQ to fire while the driver is performing non-atomic read/modify/write operations to disable, acknowledge, and re-enable that IRQ. An interrupt-handler acknowledgment write can overwrite a concurrent write that re-enables VUPDATE_NO_LOCK_EN.
What is the practical effect of the race?
The final acknowledgment write can clear VUPDATE_NO_LOCK_EN after the driver has attempted to re-enable it. This can leave that IRQ source disabled and disrupt vblank handling.
Is a fix available?
Yes. The vulnerability description states that it has been resolved by atomizing the IRQ register read/modify/write operations. A stable kernel reference is provided for commit 63e19ef3ddab806c472748c825f4dc88dcd994e8.