LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26916: Revert "drm/amd: flush any delayed gfxoff on suspend entry"

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel AMD graphics suspend deadlock. On affected systems, suspending through GNOME can trigger graphics DMA activity and hang the machine. The business impact is availability: endpoints or workstations may lock up during suspend, causing user disruption and possible unsaved work loss.

Executive priority

Treat this as a targeted availability issue, not a broad remote compromise signal. Patch through normal kernel maintenance, with higher priority for Linux desktop or workstation fleets using AMD graphics and suspend.

Technical view

The kernel fix reverts an earlier DRM/AMD change because newer amdgpu SDMA ring begin/end callbacks increased GFXOFF control usage. That made a removed suspend-entry path reachable again, allowing SDMA traffic during GNOME lockscreen-triggered suspend to deadlock the system.

Likely exposure

Exposure is most likely on Linux systems using AMDGPU/DRM AMD graphics with affected kernel builds and suspend workflows. Desktop and laptop fleets using GNOME are the clearest fit from the source description. Server exposure is less clear unless those systems use the affected AMD graphics path and suspend.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. The described trigger is local suspend behavior involving GNOME, lockscreen activity, SDMA traffic, and AMD graphics power management. No remote attack path or weaponized exploit is evidenced in the provided sources.

Researcher notes

Evidence is limited to the kernel CVE description and stable commit references. The affected-version data is sparse and severity is not scored. Validate against distribution backports rather than upstream version numbers alone.

Mitigation direction

  • Check Linux distribution advisories for a kernel including the referenced stable fixes.
  • Upgrade affected systems to a vendor-supported kernel containing the revert.
  • Prioritize AMDGPU systems where suspend or GNOME lockscreen suspend is used.
  • Temporarily avoid affected suspend workflows where operationally acceptable.
  • Track kernel package changelogs for CVE-2024-26916 or the referenced commits.

Validation and detection

  • Inventory Linux kernel versions across AMD graphics endpoints.
  • Identify systems using the amdgpu DRM driver and suspend workflows.
  • Confirm whether installed vendor kernels include one of the referenced stable commits.
  • Test suspend and resume on representative patched AMDGPU systems.
  • Monitor for post-suspend hangs or deadlocks in endpoint reports.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26916 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf94942885e8416ce9de84d8fae93684002682b5d, 78b2ba39beef21c8baebb1868569c2026ad76de0, 3aae4ef4d799fb3d0381157640fdb251008cf0ae, ab4750332dbe535243def5dcebc24ca00c1f98ac, ab4750332dbe535243def5dcebc24ca00c1f98ac, 5.15.144, 6.1.69, 6.6.8unaffected
LinuxLinux6.7, 0, 5.15.149, 6.1.79, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.