Suspend warning via unconditional ECC IRQ disable
Published Oct 22, 2025 · Updated Oct 22, 2025
Improper IRQ handling in the Linux kernel allows attackers to produce a kernel warning by initiating an AMDGPU suspend cycle. The sdma_v4_0_hw_fini path calls amdgpu_irq_put to disable ecc_irq unconditionally, including on ASICs where SDMA RAS never enabled that interrupt. The condition requires SDMA IP 4.0 hardware without SDMA ECC; the published record establishes no consequence beyond the warning or specific attacker-access requirement.
Summary
What happened
Improper IRQ handling in the Linux kernel allows attackers to produce a kernel warning by initiating an AMDGPU suspend cycle. The sdma_v4_0_hw_fini path calls amdgpu_irq_put to disable ecc_irq unconditionally, including on ASICs where SDMA RAS never enabled that interrupt. The condition requires SDMA IP 4.0 hardware without SDMA ECC; the published record establishes no consequence beyond the warning or specific attacker-access requirement.
The record
- CVE
- CVE-2023-53723
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2a179117a3b29e7136e4045c57090a05bb97f373
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3decf3a750a924362bf4e2680dd3b07242fe56e8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <71e1f44077db83e205db70a684c1f2c5d2247174
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <823787470e320f90372c3ef506769520026c571f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8b229ada2669b74fdae06c83fbfda5a5a99fc253
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c1420276be7a98df0074584bb9c1709cbc1a9df5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c5123c193696bf97fdf259c825ebfac517b54e44
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo