CVE-2026-99593: arm64: sdei: Preserve the interrupted context's exception registers

Published Nov 20, 2026
·
Updated

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

arm64: sdei: Preserve the interrupted context's exception registers

An SDEI event is dispatched by firmware regardless of PSTATE.DAIF, so it can interrupt the kernel where the exception registers are live:

- exception entry, before kernelentry has saved ELREL1/SPSREL1 and before the C handler has read ESREL1/FAREL1; - exception return, after kernelexit has loaded ELREL1/SPSREL1 and before the ERET.

An IRQ or pseudo-NMI cannot arrive there with PSTATE.I set. Firmware saves only x0-x17, PC and PSTATE around an SDEI event, so a synchronous exception taken by the handler overwrites the interrupted context's ELR, SPSR, ESR and FAR. dosdeievent() only notices that ELR changed, and warns.

The interrupted context then carries on with the handler's state. A task interrupted on its way into the kernel can be sent SIGILL for the handler's kernel data abort. A task interrupted on its way back to user space ERETs to EL1, at the handler's fixup address, with user registers loaded.

With SDEI delivering NMI backtraces, this happens in normal operation. The handler runs showregs(), which reads through possibly-NULL pointers with the nofault() accessors. printworkerinfo() faults this way for a kworker that is not running a work item, and a single sysrq-l warned once per such kworker.

Save ELR, SPSR, ESR and FAR in sdeihandler() before irqentrynmienter(), which can take an exception too, and restore them after irqentrynmiexit().

Once they are restored, a nested exception is harmless if its handler is safe in NMI context. That holds for EL1 data aborts on translation, permission and access-flag faults, which never take the mmap lock in NMI context, and for BRK. Warn once, with the syndrome, about any other exception class.

Affected Software

3 affected componentsFixes available
linux/kernel>=4.16.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Compensating control

    In arm64 SDEI __sdei_handler(), save ELR_EL1, SPSR_EL1, ESR_EL1, and FAR_EL1 before irqentry_nmi_enter(), then restore them after irqentry_nmi_exit() to preserve the interrupted context’s exception registers.

Frequently Asked Questions

1

Do interrupt masks protect against this condition?

No. Firmware can dispatch an SDEI event regardless of PSTATE.DAIF, including while normal IRQ or pseudo-NMI delivery would be blocked by PSTATE.I.

2

When is the affected state most likely to be interrupted?

The vulnerable windows are during exception entry before ELR_EL1 and SPSR_EL1 are saved or ESR_EL1 and FAR_EL1 are read, and during exception return after ELR_EL1 and SPSR_EL1 have been loaded but before ERET. SDEI delivery for NMI backtraces can reach these windows during normal operation.

3

What symptoms can indicate that an interrupted context was corrupted?

A task interrupted while entering the kernel can receive SIGILL due to the handler's kernel data abort. A task interrupted while returning to user space can ERET to EL1 at the handler's fixup address with user registers loaded.

4

Is there any runtime indication in the existing handler?

do_sdei_event() notices and warns when ELR changes. It does not detect the full corruption of ELR, SPSR, ESR, and FAR, so the warning is not a complete safeguard.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203