# CVE-2026-93254: Linux kernel arm64 interrupt handling logic fix

Source: https://junglewise.ai/threats/cve-2026-93254-in-the-linux-kernel-the-following-vulnerability-has-been-resolved  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-24. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-93254 · Severity: info · Published 2026-09-24

The Linux kernel's ARM64 architecture code contained unnecessary interrupt disable operations during kernel exit that could trigger debug warnings. This issue affects the interrupt handling path and may cause spurious warnings in kernels compiled with ARM64 priority masking debug enabled, but does not represent an exploitable security vulnerability.

Technologies: [Unknown Linux kernel](https://junglewise.ai/threats/technologies/unknown-linux-kernel). Vendors: [Unknown](https://junglewise.ai/threats/vendors/unknown).

## Quick answers

**Is CVE-2026-93254 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-93254 being exploited in the wild.

**How severe is CVE-2026-93254?** Informational severity, published 24 September 2026.

**Which products and versions are affected?** Unknown Linux kernel through 7.2.0-rc6-next-20260805.

**Is there a fix for CVE-2026-93254?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-93254 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-93254?** Check whether you run Unknown 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.

## Technical details

The vulnerability is a logic issue in arm64_exit_to_kernel_mode() where local_irq_disable() is called unconditionally before preemption checks, even in contexts where interrupts are already disabled or preemption will not occur. This confuses pNMI state tracking when CONFIG_ARM64_DEBUG_PRIORITY_MASKING=y, triggering a warning. The fix refactors the function into separate preempt and non-preempt paths to avoid redundant operations.

## Affected products

- <unknown> Linux kernel through 7.2.0-rc6-next-20260805

## Timeline

- 2026-09-24: disclosed

## Related threats

- [Linux kernel netfilter nft_byteorder multi-register bypass](https://junglewise.ai/threats/cve-2026-99285-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)
- [Linux kernel GPIO null pointer dereference in shared GPIO lookup](https://junglewise.ai/threats/cve-2026-99257-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)
- [Linux kernel NTFS race condition in page fault handler](https://junglewise.ai/threats/cve-2026-99241-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)
- [Linux kernel i915 DMC firmware load address validation bypass](https://junglewise.ai/threats/cve-2026-99146-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)
- [Linux kernel dm-integrity buffer overflow in inline mode](https://junglewise.ai/threats/cve-2026-99098-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)