CVE-2024-26916

Revert "drm/amd: flush any delayed gfxoff on suspend entry"

MEDIUM
5.5
CVSS Score
Published: April 17, 2024 at 03:59 PM UTC
Updated: June 17, 2026 at 07:18 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
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: Revert "drm/amd: flush any delayed gfxoff on suspend entry" commit ab4750332dbe ("drm/amdgpu/sdma5.2: add begin/end_use ring callbacks") caused GFXOFF control to be used more heavily and the codepath that was removed from commit 0dee72639533 ("drm/amd: flush any delayed gfxoff on suspend entry") now can be exercised at suspend again. Users report that by using GNOME to suspend the lockscreen trigger will cause SDMA traffic and the system can deadlock. This reverts commit 0dee726395333fea833eaaf838bc80962df886c8.

Affected

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

5.15.144 ≤ v < 5.15.1496.1.69 ≤ v < 6.1.796.6.8 ≤ v < 6.6.186.7 ≤ v < 6.7.66.7 ≤ v < 6.86.7.1 ≤ v < 6.7.63aae4ef4d799fb3d0381157640fdb251008cf0ae5.15.1446.1.696.6.86.76.7 rc66.7 rc76.7 rc86.8 rc16.8 rc26.8 rc36.8 rc478b2ba39beef21c8baebb1868569c2026ad76de0ab4750332dbe535243def5dcebc24ca00c1f98acf94942885e8416ce9de84d8fae93684002682b5d
Vendor states this is fixed in 65158edb0a3a8df23197d52cd24287e39eaf95d6 (fixed)
Vendor states this is fixed in 916361685319098f696b798ef1560f69ed96e934 (fixed)
Vendor states this is fixed in caa2565a2e13899be31f7b1e069e6465d3e2adb0 (fixed)
Vendor states this is fixed in d855ceb6a5fde668c5431156bc60fae0cc52b764 (fixed)
Vendor states this is fixed in ff70e6ff6fc2413caf33410af7462d1f584d927e (fixed)
Vendor states this is fixed in 5.15.149 (unaffected)
Vendor states this is fixed in 6.1.79 (unaffected)
Vendor states this is fixed in 6.6.18 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)
Vendor states this is fixed in 6.7.6 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/65158edb0a3a8df23197d52cd24287e39eaf95d6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/916361685319098f696b798ef1560f69ed96e934
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/caa2565a2e13899be31f7b1e069e6465d3e2adb0
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d855ceb6a5fde668c5431156bc60fae0cc52b764
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ff70e6ff6fc2413caf33410af7462d1f584d927e

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card