irqchip/gic-v5: Immediately exec priority drop following activate

Overview

In the Linux kernel, the following vulnerability has been resolved:

irqchip/gic-v5: Immediately exec priority drop following activate

With GICv5 an interrupt of equal or lower priority cannot be signalled until there has been a priority drop. This is done via the GIC CDEOI system instruction. Once this has been executed, the hardware is able to signal the next interrupt if there is one.

As all interrupts are programmed to have the same priority, no new interrupts can be signalled until the priority drop has happened. This can cause issues when, for example, an interrupt remains active while a long running process takes place, such as when injecting a physical interrupt into a guest VM in software.

The GICv5 driver has so far done the priority drop as part of irq_eoi(), i.e., at the same time as deactivating the interrupt. This means that any long running process (or VM) could block incoming interrupts, effectively causing a denial of service for all other interrupts.

Rather than doing the EOI as part of irq_eoi() (which the name would suggest would be a good place for it), move it to happen immediately after acknowledging an interrupt in the main GICv5 interrupt handler. The deactivation of interrupts (GIC CDDI) remains implemented as part of irq_eoi(), which means that the same interrupt cannot be signalled a second time until deactivated by software.

Affected

• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c29bb5acd0cad0b49399d1399dd1bacb39e41438
• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < abf60331ebe9a9a7937a72aac7699c2907ab9307
• Linux < 6.18.53
• Linux (all versions)

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.