All reports
Low

kernel: drm/fb-helper: Only consider active CRTCs for vblank sync

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-72313

Probability of exploitation in the next 30 days: 0.20%

FIRST EPSS · 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: drm/fb-helper: Only consider active CRTCs for vblank sync Only synchronize fbdev output to the vblank of an active CRTC. Go over the list of CRTCs and pick the first that matches. Fixes warnings as the one shown below [ 77.201354] WARNING: drivers/gpu/drm/drm_vblank.c:1320 at drm_crtc_wait_one_vblank+0x194/0x1cc [drm], CPU#1: kworker/1:7/1867 [ 77.201354] omapdrm omapdrm.0: [drm] vblank wait timed out on crtc 0 This currently happens if the fbdev output is not on CRTC 0. Atomic and non-atomic drivers require distinct code paths. As for other fbdev operations, implement both and select the correct one at runtime. Not finding an active CRTC is not a bug. Do not wait in this case, but flush the display update as before. v4:

A flaw was found in the Linux kernel's display rendering manager (DRM) framebuffer helper (drm/fb-helper). This vulnerability arises from incorrect synchronization with display controllers (CRTCs), where the system attempts to synchronize with an inactive controller. This can lead to display timeouts and potential system unresponsiveness, resulting in a Denial of Service (DoS).