This kernel flaw causes the priority drop to be performed along with the interrupt end‑of‑interrupt handling. Because all GICv5 interrupts are configured with the same priority, the hardware does not signal a new interrupt until the priority drop has occurred. If a process or a guest virtual machine remains active for a long time, the priority drop stays pending and new interrupts cannot be serviced, effectively denying all other interrupt‑driven work.

The weakness affects all Linux kernel configurations that use the GICv5 driver with the default priority drop logic. All versions prior to the commit that moves the priority drop immediately after interrupt acknowledge are vulnerable, regardless of the specific Linux distribution.

The vulnerability leads to a denial of service for all pending interrupts. The CVSS score is 5.5, the EPSS score is <1%, and the vulnerability is not listed in CISA KEV. Based on the description, the likely attack vector is a privileged process or a virtual machine that can generate long‑running interrupts; the attacker can trigger the denial of service by keeping an interrupt active while executing a workload that prevents the priority drop from occurring. The impact is local, affecting only the host system’s interrupt handling, but can be critical for real‑time or virtualization workloads.