LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53628: drm/amdgpu: drop gfx_v11_0_cp_ecc_error_irq_funcs

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: drop gfx_v11_0_cp_ecc_error_irq_funcs The gfx.cp_ecc_error_irq is retired in gfx11. In gfx_v11_0_hw_fini still use amdgpu_irq_put to disable this interrupt, which caused the call trace in this function. [ 102.873958] Call Trace: [ 102.873959] <TASK> [ 102.873961] gfx_v11_0_hw_fini+0x23/0x1e0 [amdgpu] [ 102.874019] gfx_v11_0_suspend+0xe/0x20 [amdgpu] [ 102.874072] amdgpu_device_ip_suspend_phase2+0x240/0x460 [amdgpu] [ 102.874122] amdgpu_device_ip_suspend+0x3d/0x80 [amdgpu] [ 102.874172] amdgpu_device_pre_asic_reset+0xd9/0x490 [amdgpu] [ 102.874223] amdgpu_device_gpu_recover.cold+0x548/0xce6 [amdgpu] [ 102.874321] amdgpu_debugfs_reset_work+0x4c/0x70 [amdgpu] [ 102.874375] process_one_work+0x21f/0x3f0 [ 102.874377] worker_thread+0x200/0x3e0 [ 102.874378] ? process_one_work+0x3f0/0x3f0 [ 102.874379] kthread+0xfd/0x130 [ 102.874380] ? kthread_complete_and_exit+0x20/0x20 [ 102.874381] ret_from_fork+0x22/0x30 v2: - Handle umc and gfx ras cases in separated patch - Retired the gfx_v11_0_cp_ecc_error_irq_funcs in gfx11 v3: - Improve the subject and code comments - Add judgment on gfx11 in the function of amdgpu_gfx_ras_late_init v4: - Drop the define of CP_ME1_PIPE_INST_ADDR_INTERVAL and SET_ECC_ME_PIPE_STATE which using in gfx_v11_0_set_cp_ecc_error_state - Check cp_ecc_error_irq.funcs rather than ip version for a more sustainable life v5: - Simplify judgment conditions

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel AMDGPU driver reliability flaw. On some AMD gfx11 GPU systems, the driver tries to disable a retired interrupt during shutdown, suspend, or recovery paths, causing a kernel call trace. Business impact is likely availability and operational stability, not data theft, based on the provided evidence.

Executive priority

Treat as a targeted stability patch for AMD GPU Linux hosts. Prioritize affected workstations, GPU compute nodes, or systems where GPU recovery failures affect operations. Escalate if internal logs show matching call traces.

Technical view

The AMDGPU gfx11 code still called amdgpu_irq_put for gfx.cp_ecc_error_irq even though that interrupt is retired in gfx11. The fix removes the retired IRQ functions and checks cp_ecc_error_irq.funcs. The source shows call traces in gfx_v11_0_hw_fini during suspend or GPU recovery handling.

Likely exposure

Exposure appears limited to Linux systems using the AMDGPU driver on affected kernel builds and gfx11-class AMD GPUs. The bundle lists Linux 6.3-related versions and specific kernel commits, but does not provide a complete distro package matrix.

Exploitation context

The sources do not show active exploitation, and KEV is false. The described trigger is a driver lifecycle or recovery path producing a call trace, not a documented remote attack path. No public exploit status is provided in the bundle.

Researcher notes

Evidence is narrow but specific: retired gfx11 CP ECC IRQ handling remained wired into fini paths. Severity, CVSS, CWE, and complete affected-version semantics are absent, so avoid broader impact claims beyond AMDGPU reliability until vendor advisories clarify.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported AMDGPU fixes.
  • Prioritize systems with AMD gfx11 GPUs and kernel 6.3-era builds.
  • If updates are unavailable, follow vendor guidance for operational mitigations.

Validation and detection

  • Inventory Linux kernel versions and AMDGPU hardware models.
  • Confirm the fixed commits are present in deployed kernel source or changelog.
  • Review kernel logs for gfx_v11_0_hw_fini or amdgpu call traces.
  • Test suspend, reset, and GPU recovery workflows after patching.
Prepared
Confidence
medium
Sources
4

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-53628 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux790bef488b4ac4ceb52f5cda2a67c0d9bbb56d8c, 790bef488b4ac4ceb52f5cda2a67c0d9bbb56d8cunaffected
LinuxLinux6.3, 0, 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.