The vulnerability arises from the kernel’s DRM/fb-helper module synchronizing framebuffer output to the vertical‑blank period of an inactive CRTC. Because the module scans the list of CRTCs for the first active match, it can incorrectly synchronize to a CRTC with no vblank signal, causing a timeout warning and potentially a deadlock that blocks display updates. The bug is confined to how the DRM subsystem deals with active versus inactive CRTCs and does not provide a remote attack vector beyond temporary display instability.

Any Linux kernel build that has not incorporated the patch that limits vblank synchronization to an active CRTC may be affected. The CVE does not specify a version range, but all kernels compiled from the commit timeframe referenced by the linked patches could exhibit this behavior until the fix is delivered to distributions.

The EPSS score is < 1%, and the vulnerability is not listed in the CISA KEV catalog, suggesting no known active exploitation. Because the flaw mainly leads to a kernel warning or deadlock when a framebuffer is attached to a non‑active CRTC, the likelihood of malicious privilege escalation is low. The CVSS score is 5.5, so the risk profile remains a moderate severity concern rather than a high‑severity security flaw. Systems that rely on framebuffer devices should keep their kernel up to date to eliminate this defect.