CVE-2026-98878

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

Description

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.

Key facts

Published
23 Oct 2026
Last changed
26 Oct 2026
Assigned by
Linux
EPSS
0.192% likely to be exploited in the next 30 days, higher than 8.916% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 7ec80fb3f025825e860b433685fb801d6de34bf3 up to but excluding c29bb5acd0cad0b49399d1399dd1bacb39e41438 (affected)
  • 7ec80fb3f025825e860b433685fb801d6de34bf3 up to but excluding abf60331ebe9a9a7937a72aac7699c2907ab9307 (affected)
LinuxLinux
  • Default status: affected
  • 6.17 (affected)
  • 0 up to but excluding 6.17 (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References