# CVE-2026-92513: RDMA/mana_ib: drain QP references after partial table insertion

> A race condition in the Linux kernel mana_ib driver allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-92513, DEBIAN-CVE-2026-92513, GHSA-r87w-wp8m-2wvh, UBUNTU-CVE-2026-92513

## What is CVE-2026-92513?

CVE-2026-92513 is an use after free vulnerability in Linux, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

RDMA/mana_ib: drain QP references after partial table insertion

mana_table_store_ud_qp() publishes a QP at its send-queue id before
inserting the receive-queue id, dropping the XArray lock between the two
xa_insert_irq() calls. A concurrent completion handler can look up the QP
and take a transient reference. When the second insertion fails, the
rollback erased only the send-queue entry and returned, leaving both the
initial table reference and the transient reference outstanding while RDMA
core frees the QP, causing a use-after-free.

Drain the reference as normal destruction does: drop the initial reference
and wait for qp->free, releasing the QP only after every concurrent lookup
returns its reference.

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


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

Apply the vendor's patch.

## Is CVE-2026-92513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92513 is an use after free vulnerability in Linux, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92513 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-92513/ (Markdown: https://insights.sbomify.com/CVE-2026-92513/index.md)
```

## Sources

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

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