LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53237: drm/amdgpu: fix amdgpu_irq_put call trace in gmc_v11_0_hw_fini

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix amdgpu_irq_put call trace in gmc_v11_0_hw_fini The gmc.ecc_irq is enabled by firmware per IFWI setting, and the host driver is not privileged to enable/disable the interrupt. So, it is meaningless to use the amdgpu_irq_put function in gmc_v11_0_hw_fini, which also leads to the call trace. [ 102.980303] Call Trace: [ 102.980303] <TASK> [ 102.980304] gmc_v11_0_hw_fini+0x54/0x90 [amdgpu] [ 102.980357] gmc_v11_0_suspend+0xe/0x20 [amdgpu] [ 102.980409] amdgpu_device_ip_suspend_phase2+0x240/0x460 [amdgpu] [ 102.980459] amdgpu_device_ip_suspend+0x3d/0x80 [amdgpu] [ 102.980520] amdgpu_device_pre_asic_reset+0xd9/0x490 [amdgpu] [ 102.980573] amdgpu_device_gpu_recover.cold+0x548/0xce6 [amdgpu] [ 102.980687] amdgpu_debugfs_reset_work+0x4c/0x70 [amdgpu] [ 102.980740] process_one_work+0x21f/0x3f0 [ 102.980741] worker_thread+0x200/0x3e0 [ 102.980742] ? process_one_work+0x3f0/0x3f0 [ 102.980743] kthread+0xfd/0x130 [ 102.980743] ? kthread_complete_and_exit+0x20/0x20 [ 102.980744] ret_from_fork+0x22/0x30

MediumCVSS 5.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the AMDGPU driver. A firmware-controlled ECC interrupt is handled incorrectly during GPU shutdown/recovery paths, producing a kernel call trace and potential availability impact. It is local, not remotely exploitable from the network based on the supplied CVSS vector.

Executive priority

Treat this as a moderate availability issue. It does not indicate remote compromise or data theft from the provided sources, but it can affect reliability of Linux hosts using AMD GPUs. Remediate through normal kernel patch cycles, faster for shared GPU infrastructure.

Technical view

The vulnerability is in drm/amdgpu gmc_v11_0_hw_fini. The driver calls amdgpu_irq_put for gmc.ecc_irq even though firmware controls that interrupt, causing a call trace during suspend, ASIC reset, or GPU recovery flows. CVSS is 5.5 with local attack vector and high availability impact.

Likely exposure

Exposure is most likely on Linux systems using affected kernel versions with AMD GPUs and the amdgpu driver. The provided affected data names Linux kernel versions including 6.3, 6.1.29, 6.2.16, 6.3.3, and 6.4, but distro backports may alter exposure.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The CVSS vector requires local privileges and no user interaction. Practical risk is availability disruption on systems where a local user or operational condition can reach GPU suspend, reset, or recovery paths.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. No CWE, exploit report, or detailed affected-version range semantics are provided. Confirm exposure against actual distro kernel packages because Linux vendors commonly backport fixes without changing upstream version numbers.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable amdgpu fix commits.
  • Use distribution vendor guidance to confirm whether fixes are backported.
  • Prioritize AMD GPU systems with local multi-user access or GPU workloads.
  • If updates are unavailable, monitor for kernel call traces during GPU recovery.
  • Schedule remediation to avoid disrupting GPU-dependent production workloads.

Validation and detection

  • Inventory Linux kernel versions on AMD GPU hosts.
  • Confirm whether the amdgpu driver is loaded on candidate systems.
  • Check vendor kernel changelogs for the referenced stable commits or backports.
  • Review kernel logs for gmc_v11_0_hw_fini or amdgpu_irq_put call traces.
  • After updating, validate normal suspend, reset, and GPU workload recovery behavior.
Prepared
Confidence
medium
Sources
6

Public sources used

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-53237 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-53237Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbef774effb278ff0b65ea2dbaa1ab32ba6a1dc13, 56a03f64fedf49a4f81c5605167b6e7bb0300a59, c8b5a95b570949536a2b75cd8fc4f1de0bc60629, c8b5a95b570949536a2b75cd8fc4f1de0bc60629, 6.1.26, 6.2.13unaffected
LinuxLinux6.3, 0, 6.1.29, 6.2.16, 6.3.3, 6.4affected
Weakness

CWE details

No CWE listed

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