LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54261: drm/amdkfd: Add missing gfx11 MQD manager callbacks

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Add missing gfx11 MQD manager callbacks mqd_stride function was introduced in commit 2f77b9a242a2 ("drm/amdkfd: Update MQD management on multi XCC setup") but not assigned for gfx11. Fixes a NULL dereference in debugfs.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-54261 is a Linux kernel AMD GPU driver bug where missing callback wiring can trigger a NULL pointer dereference through debugfs. The provided sources do not show data theft, privilege escalation, remote attack, or active exploitation.

Executive priority

Handle through normal kernel patch governance unless affected systems expose debugfs to untrusted users. There is no source-backed evidence of active exploitation or high business impact, but shared compute hosts deserve earlier review.

Technical view

The issue is in drm/amdkfd for gfx11. A previously introduced mqd_stride function was not assigned for gfx11 MQD management, causing a NULL dereference in debugfs. The listed stable kernel commits provide the upstream fix.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with AMD KFD/gfx11 code paths. Practical exposure depends on kernel build, hardware, debugfs availability, and distribution backports. The source bundle does not identify affected distributions.

Exploitation context

CISA KEV status is false in the bundle, and no cited source states active exploitation. The sources only support a debugfs-triggered NULL dereference, not remote exploitation or broader compromise.

Researcher notes

Impact evidence is incomplete: no CVSS, CWE, or exploitability details are provided. Analysis should stay anchored to the kernel commits and CVE record. Avoid assuming distribution impact without vendor confirmation.

Mitigation direction

  • Review Linux vendor advisories for backported fixes in your distribution kernel.
  • Upgrade to a kernel package containing the referenced stable commits.
  • Limit debugfs availability to trusted administrators where operationally feasible.
  • Prioritize affected GPU compute or shared Linux systems first.

Validation and detection

  • Inventory Linux hosts with AMD GPU/KFD support and affected kernel lines.
  • Confirm whether vendor kernel changelogs include the referenced stable commits.
  • Check whether debugfs is enabled or accessible on in-scope systems.
  • Document systems deferred from patching and their compensating controls.
Prepared
Confidence
medium
Sources
4

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-2023-54261 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
0ADP providers
3Source links

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2f77b9a242a2e01822efc80c8b63eaa31df0f8b4, 2f77b9a242a2e01822efc80c8b63eaa31df0f8b4unaffected
LinuxLinux6.5, 0, 6.5.4, 6.6affected
Weakness

CWE details

No CWE listed

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