Quick answers
- Is CVE-2026-98395 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98395 being exploited in the wild.
- How severe is CVE-2026-98395?
- Informational severity, published 14 October 2026.
- Which products and versions are affected?
- Linux kernel versions prior to fix (CVE-2026-98395).
- Is there a fix for CVE-2026-98395?
- Yes: fixed in Linux kernel versions with commit fixing arch_interrupt_async_exit_prepare() to use hard_irq_disable(). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-98395 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-98395?
- Check whether you run Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Linux kernel versions with commit fixing arch_interrupt_async_exit_prepare() to use hard_irq_disable()
Technical details
The vulnerability exists in __replay_soft_interrupts() where the handler's exit path calls arch_interrupt_async_exit_prepare(), which unconditionally sets irq_soft_mask to IRQS_DISABLED (0x1), stripping the IRQS_PMI_DISABLED (0x2) bit. Since replayed interrupts bypass the normal arch_interrupt_enter_prepare() entry point, the mask remains corrupted at 0x1 instead of IRQS_ALL_DISABLED (0x3), triggering WARN_ON checks in next_interrupt(). The fix replaces local_irq_disable() with hard_irq_disable() to properly preserve the full soft mask state on PPC64 and correctly disable interrupts on PPC32.
Affected products
- Linux Kernel versions prior to fix (CVE-2026-98395)
Timeline
- 2026-10-14: disclosed