# CVE-2026-98353: RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables

> A race condition in the Linux kernel RDMA erdma driver can cause a deadlock and system hang when interrupts occur during queue pair creation.

- **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:** 6 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-106194, BELL-CVE-2026-98353, DEBIAN-CVE-2026-98353, GHSA-c26j-r98f-9j66, UBUNTU-CVE-2026-98353

## What is CVE-2026-98353?

CVE-2026-98353 is a vulnerability in Linux, published on 6 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/erdma: Use IRQ-safe XArray helpers for QP and CQ tables

Locked QP and CQ lookups from EQ interrupts can deadlock with
create-path XArray updates. If an interrupt arrives while the create
path holds the plain xa_lock, the lookup spins forever trying to
acquire the same lock.

Use IRQ-safe XArray helpers for all QP and CQ create-path updates,
including the GSI QP store and error paths. Initialize both arrays with
XA_FLAGS_LOCK_IRQ so sleeping allocations preserve interrupt state.

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


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

Apply the vendor's patch.

## Is CVE-2026-98353 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98353 is a vulnerability in Linux, published on 6 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-98353 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-98353/ (Markdown: https://insights.sbomify.com/CVE-2026-98353/index.md)
```

## Sources

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

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