Kernel call trace via unmatched interrupt release
Published Oct 1, 2025 · Updated Oct 1, 2025
Improper interrupt handling in the Linux kernel amdgpu GFX9 driver allows local users to trigger a kernel call trace during system suspend. The gfx_v9_0_hw_fini function calls amdgpu_irq_put for cp_ecc_error_irq even when legacy GFX RAS never enabled that interrupt. Reaching the path requires CAP_SYS_ADMIN in the initial user namespace and compatible AMD GFX9 hardware; the published trace shows a warning, not a demonstrated crash.
Summary
What happened
Improper interrupt handling in the Linux kernel amdgpu GFX9 driver allows local users to trigger a kernel call trace during system suspend. The gfx_v9_0_hw_fini function calls amdgpu_irq_put for cp_ecc_error_irq even when legacy GFX RAS never enabled that interrupt. Reaching the path requires CAP_SYS_ADMIN in the initial user namespace and compatible AMD GFX9 hardware; the published trace shows a warning, not a demonstrated crash.
The record
- CVE
- CVE-2023-53471
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 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 <20ca90ceda71ed90a4d6960acbe7d5e120b40c0d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3d28af21a874c5123d1681c2d686627f7ff7e488
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4a76680311330aefe5074bed8f06afa354b85c48
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <625d4112ea25dbad7ddf749fd5c1287ceffb2339
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cd3c0f7013c37cd24fc40b601319007f136c1201
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <efce310db74fdc6d2acd959f3582972ae4a8d7d5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f661ad53658a1ea35c004af1f5fbe25c4d1cdb08
What conditions does exploitation require?
What is affected?
Published CVSS scores
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