CVE-2024-36944

Reapply "drm/qxl: simplify qxl_fence_wait"

MEDIUM

5.5

CVSS Score

Published: May 30, 2024 at 03:35 PM UTC

Updated: June 17, 2026 at 07:37 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: Reapply "drm/qxl: simplify qxl_fence_wait" This reverts commit 07ed11afb68d94eadd4ffc082b97c2331307c5ea. Stephen Rostedt reports: "I went to run my tests on my VMs and the tests hung on boot up. Unfortunately, the most I ever got out was: [ 93.607888] Testing event system initcall: OK [ 93.667730] Running tests on all trace events: [ 93.669757] Testing all events: OK [ 95.631064] ------------[ cut here ]------------ Timed out after 60 seconds" and further debugging points to a possible circular locking dependency between the console_owner locking and the worker pool locking. Reverting the commit allows Steve's VM to boot to completion again. [ This may obviously result in the "[TTM] Buffer eviction failed" messages again, which was the reason for that original revert. But at this point this seems preferable to a non-booting system... ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

5.15.156 ≤ v < 5.15.1596.1.87 ≤ v < 6.1.916.6.28 ≤ v < 6.6.316.8.7 ≤ v < 6.8.1013ab5db42a593f9904acc39055ee3ae75963fc8842cbe04a5c77da74fb7161b0ae63f1f6e105d6335.15.156 6.1.87 6.6.28 6.8.7 6.9 rc1 6.9 rc2 6.9 rc3 6.9 rc4 6.9 rc5 6.9 rc6 6.9 rc77ed11afb68d94eadd4ffc82b97c2331307c5ea84fb60063509e462e39c0e097c7d6dbb71c959678d278fc34cdd8a44e995fa93dfd31d619a2e1fe6

Vendor states this is fixed in 148ed8b4d64f94ab079c8f0d88c3f444db97ba97 (fixed)

Vendor states this is fixed in 3628e0383dd349f02f882e612ab6184e4bb3dc10 (fixed)

Vendor states this is fixed in 3dfe35d8683daf9ba69278643efbabe40000bbf6 (fixed)

Vendor states this is fixed in 4a89ac4b0921c4ea21eb1b4cf3a469a91bacfcea (fixed)

Vendor states this is fixed in b548c53bc3ab83dc6fc86c8e840f013b2032267a (fixed)

Affected range stops below 5.15.159, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.1.91, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.6.31, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.8.10, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references