CVE-2026-98430: RDMA/efa: Keep admin queues alive while IRQ is registered

Published Oct 14, 2026
·
Updated

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

RDMA/efa: Keep admin queues alive while IRQ is registered

The management IRQ handler accesses both the admin completion queue and the async event queue. The driver registered the IRQ before constructing these queues and destroyed them before freeing the IRQ, so the handler's lifetime was not contained by the resources it accesses.

Initialize the queues with interrupts masked, request the IRQ, and then switch to interrupt mode. On removal, reset the device and free the IRQ before destroying the queues. Also reset the device before destroying the queues if IRQ registration fails, because the device already has their DMA addresses.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Update the EFA driver resource lifecycle so admin and asynchronous event queues are initialized with interrupts masked, the IRQ is requested before switching to interrupt mode, and the queues remain alive until the IRQ is freed; on device removal, reset the device before destroying the queues and freeing the IRQ.

Event History

Oct 14, 2026
CVE Published
via MITRE·01:27 PM
Data Sourced
via MITRE·01:27 PM
Description

Frequently Asked Questions

1

When can this issue be triggered?

The unsafe lifetime window exists during EFA driver initialization and removal. It can also occur after IRQ registration fails, because the device may already hold DMA addresses for the admin queues.

2

What resources are involved in the race?

The management IRQ handler accesses the admin completion queue and async event queue. Previously, the IRQ could be registered before those queues were constructed or remain registered after they were destroyed.

3

What is the relevant remediation behavior?

The corrected sequence initializes queues with interrupts masked, registers the IRQ, and only then enables interrupt mode. During removal, the device is reset and the IRQ is freed before the queues are destroyed.

4

What should be done if IRQ registration fails during initialization?

Reset the device before destroying the queues. This is necessary because the device may already have DMA addresses pointing to those queue resources.

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