CVE-2026-90304: ARM: 9484/1: enable interrupts when unhandled user faults are triggered

Published Sep 17, 2026
·
Updated

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

ARM: 9484/1: enable interrupts when unhandled user faults are triggered

PREEMPTRT requires interrupts to be enabled when sending signals.

When doDataAbort()/doPrefetchAbort() triggers unhandled user faults, that is inf->fn() return a non-zero value, and the interrupts are not enabled within the hook function, forcesigfault() will be called with interrupts disabled.

This can be triggered by user programs executing the bkpt instruction, with kernel config CONFIGPERFEVENTS=n.

Enable interrupts in doDataAbort()/doPrefetchAbort() when unhandled user faults are triggered to fix the issue.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Update the ARM fault handlers to enable interrupts in do_DataAbort()/do_PrefetchAbort() when handling unhandled user faults so that PREEMPT_RT can send signals correctly (fix for the case where force_sig_fault() is invoked via inf->fn() non-zero while interrupts would otherwise remain disabled, particularly when CONFIG_PERF_EVENTS=n).

    Linux kernel (ARM) PREEMPT_RT Interrupt handling for unhandled user faults in do_DataAbort()/do_PrefetchAbort() = enabled

Event History

Sep 17, 2026
CVE Published
via MITRE·04:08 PM
Data Sourced
via MITRE·04:08 PM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

The issue affects ARM Linux kernel systems using PREEMPT_RT where unhandled user faults reach force_sig_fault() with interrupts disabled. The described trigger specifically requires CONFIG_PERF_EVENTS=n.

2

What is required to trigger the vulnerable path?

A user program can trigger it by executing the bkpt instruction. The fault must be unhandled, meaning the relevant fault hook returns a non-zero value without enabling interrupts.

3

Are systems with performance events enabled affected by the described trigger?

The provided trigger is specifically stated for kernels built with CONFIG_PERF_EVENTS=n. The data does not establish that the same bkpt-based path is reachable when performance events are enabled.

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