CVE-2026-98878: Linux kernel · irqchip/gic-v5: Immediately exec priority drop following activate
Source GCVE Database
Not known to be exploited : upgrade to c29bb5acd0cad0b49399d1399dd1bacb39e41438 or abf60331ebe9a9a7937a72aac7699c2907ab9307 soon.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c29bb5acd0cad0b49399d1399dd1bacb39e41438, abf60331ebe9a9a7937a72aac7699c2907ab9307
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to c29bb5acd0cad0b49399d1399dd1bacb39e41438 or abf60331ebe9a9a7937a72aac7699c2907ab9307.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to move the priority drop to immediately after interrupt acknowledgment in the GICv5 driver. Users should update to the fixed kernel version once available. No other mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's GICv5 interrupt controller driver caused a delay in priority dropping after interrupt activation, potentially blocking new interrupts and causing a denial of service. The issue was due to the priority drop being performed during interrupt deactivation instead of immediately after acknowledgment. This was fixed by moving the priority drop to occur right after interrupt acknowledgment in the main interrupt handler.