Linux Kernel up to 7.1.4/7.2-rc2 drm/fb-helper drm_vblank.c drm_crtc_wait_one_vblank deadlock

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.1.4/7.2-rc2. It has been declared as critical. This vulnerability affects the function drm_crtc_wait_one_vblank of the file drivers/gpu/drm/drm_vblank.c of the component drm/fb-helper. The manipulation results in deadlock. This vulnerability is known as CVE-2026-72313. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 7.1.4/7.2-rc2. Affected is the function drm_crtc_wait_one_vblank of the file drivers/gpu/drm/drm_vblank.c of the component drm/fb-helper. The manipulation with an unknown input leads to a deadlock vulnerability. CWE is classifying the issue as CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. This is going to have an impact on availability. CVE summarizes:

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: - avoid possible deadlocks with locking context (Sashiko) v3: - drop excessive state validation (Jani) - acquire plane and CRTC mutices (Sashiko) v2: - move look-up code into separate helper - support drivers with legacy modesetting v1: - see https://lore.kernel.org/dri-devel/[email protected]/

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2026-72313 since 08/09/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/15/2026). This vulnerability is assigned to T1499 by the MITRE ATT&CK project.

Upgrading to version 7.1.5 or 7.2-rc3 eliminates this vulnerability. Applying the patch 7d84acf641afb68aa8efe40815ef43779ddb12fd/06c2b8d7ea2bcb014dd974fc3bc6d128d65d7477 is able to eliminate this problem.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 7.1.0
• 7.1.1
• 7.1.2
• 7.1.3
• 7.1.4
• 7.2-rc1
• 7.2-rc2

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion