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

> A race condition in the Linux kernel EFA driver allows local attackers to cause a denial of service by triggering a use-after-free in the IRQ handler.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108164, BELL-CVE-2026-98430, DEBIAN-CVE-2026-98430, GHSA-qx8x-g48g-m39m, UBUNTU-CVE-2026-98430

## What is CVE-2026-98430?

CVE-2026-98430 is a vulnerability in Linux, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-98430?


## How do I fix CVE-2026-98430?

Apply the vendor's patch.

## Is CVE-2026-98430 being exploited?

There is no known exploitation of CVE-2026-98430 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98430 and fix it if it is affected.

What it is: CVE-2026-98430 is a vulnerability in Linux, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98430 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98430/ (Markdown: https://insights.sbomify.com/CVE-2026-98430/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98430
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98430
- OSV: https://osv.dev/vulnerability/CVE-2026-98430

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98430/
Summaries are generated and may contain mistakes; the official description above is the record.