CVE-2024-46820

What it actually does

Incorrect calls to disable VCN IRQ and set its state in the vcn 5.0.0 suspend path trigger a WARN_ON(!amdgpu_irq_enabled) inside amdgpu_irq_put because VCN 5 never enables IRQs through that mechanism.

Why it matters to the business

Produces spurious kernel warnings during suspend on AMD GPUs using VCN 5 hardware; no denial of service, privilege escalation, or data exposure results, but may increase log noise and complicate incident response on affected systems.

How an attack unfolds

No attacker-controlled input or code path exists; the condition is reached only during normal kernel suspend of an AMD VCN 5 device and simply emits a warning.

How to fix it

Update the Linux kernel to a version containing commit aa92264ba6fd4fb570002f69762634221316e7ae or an equivalent stable backport; rebuild and reboot with the updated kernel.

How to confirm the fix worked

Boot the patched kernel, trigger a suspend/resume cycle on an AMD VCN 5 system, and confirm the WARN_ON message no longer appears in the kernel log.

How to detect it

Search kernel logs (dmesg, journalctl) for the string WARN_ON(!amdgpu_irq_enabled(adev, src, type)) occurring during VCN-related suspend sequences.

What your security team should do

• Apply the referenced kernel commit or newer stable release at the next maintenance window
• Add a temporary log filter for the amdgpu_irq_put warning until patches are deployed