CVE-2023-53723

drm/amdgpu: disable sdma ecc irq only when sdma RAS is enabled in suspend

N/A
Published: October 22, 2025 at 01:23 PM UTC
Updated: October 28, 2026 at 07:10 PM 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
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: disable sdma ecc irq only when sdma RAS is enabled in suspend sdma_v4_0_ip is shared on a few asics, but in sdma_v4_0_hw_fini, driver unconditionally disables ecc_irq which is only enabled on those asics enabling sdma ecc. This will introduce a warning in suspend cycle on those chips with sdma ip v4.0, while without sdma ecc. So this patch correct this. [ 7283.166354] RIP: 0010:amdgpu_irq_put+0x45/0x70 [amdgpu] [ 7283.167001] RSP: 0018:ffff9a5fc3967d08 EFLAGS: 00010246 [ 7283.167019] RAX: ffff98d88afd3770 RBX: 0000000000000001 RCX: 0000000000000000 [ 7283.167023] RDX: 0000000000000000 RSI: ffff98d89da30390 RDI: ffff98d89da20000 [ 7283.167025] RBP: ffff98d89da20000 R08: 0000000000036838 R09: 0000000000000006 [ 7283.167028] R10: ffffd5764243c008 R11: 0000000000000000 R12: ffff98d89da30390 [ 7283.167030] R13: ffff98d89da38978 R14: ffffffff999ae15a R15: ffff98d880130105 [ 7283.167032] FS: 0000000000000000(0000) GS:ffff98d996f00000(0000) knlGS:0000000000000000 [ 7283.167036] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 7283.167039] CR2: 00000000f7a9d178 CR3: 00000001c42ea000 CR4: 00000000003506e0 [ 7283.167041] Call Trace: [ 7283.167046] <TASK> [ 7283.167048] sdma_v4_0_hw_fini+0x38/0xa0 [amdgpu] [ 7283.167704] amdgpu_device_ip_suspend_phase2+0x101/0x1a0 [amdgpu] [ 7283.168296] amdgpu_device_suspend+0x103/0x180 [amdgpu] [ 7283.168875] amdgpu_pmops_freeze+0x21/0x60 [amdgpu] [ 7283.169464] pci_pm_freeze+0x54/0xc0

Affected

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

4.2d38ceaf99ed015f2a0b9af3499791bd3a3daae21
Vendor states this is fixed in 2a179117a3b29e7136e4045c57090a05bb97f373 (fixed)
Vendor states this is fixed in 3decf3a750a924362bf4e2680dd3b07242fe56e8 (fixed)
Vendor states this is fixed in 71e1f44077db83e205db70a684c1f2c5d2247174 (fixed)
Vendor states this is fixed in 823787470e320f90372c3ef506769520026c571f (fixed)
Vendor states this is fixed in 8b229ada2669b74fdae06c83fbfda5a5a99fc253 (fixed)
Vendor states this is fixed in c1420276be7a98df0074584bb9c1709cbc1a9df5 (fixed)
Vendor states this is fixed in c5123c193696bf97fdf259c825ebfac517b54e44 (fixed)
Vendor states this is fixed in 4.2 (unaffected)
Vendor states this is fixed in 5.10.180 (unaffected)
Vendor states this is fixed in 5.15.112 (unaffected)
Vendor states this is fixed in 5.4.243 (unaffected)
Vendor states this is fixed in 6.1.29 (unaffected)
Vendor states this is fixed in 6.2.16 (unaffected)
Vendor states this is fixed in 6.3.3 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

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