# CVE-2026-92514: RDMA/erdma: Fix CEQ tasklet use-after-free on removal

> A use-after-free in the Linux kernel RDMA erdma driver allows local attackers to execute code or cause a denial of service during device removal.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102210, BELL-CVE-2026-92514, DEBIAN-CVE-2026-92514, GHSA-mcv5-xwww-xj32, UBUNTU-CVE-2026-92514

## What is CVE-2026-92514?

CVE-2026-92514 is an use after free vulnerability in Linux, published on 17 Sep 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: Fix CEQ tasklet use-after-free on removal

Each CEQ interrupt handler only schedules eqc->tasklet. The tasklet calls
erdma_ceq_completion_handler(), which reads the DMA-coherent EQ ring
through get_next_valid_eqe() and updates eq->dbrec through notify_eq().

erdma_ceqs_uninit() frees each CEQ IRQ and then destroys its EQ.
free_irq() prevents another hard IRQ and waits for an in-flight handler,
but it does not drain a tasklet that the handler already scheduled. The
tasklet can therefore access eq->qbuf or eq->dbrec after
erdma_eq_destroy() frees them.

Clearing ceq_cb->ready does not synchronize with a tasklet that already
passed the check at the start of erdma_ceq_completion_handler().

Kill the tasklet after free_irq(), when no handler can schedule it again,
and before erdma_ceq_uninit_one() releases the EQ buffers.

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


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

Apply the vendor's patch.

## Is CVE-2026-92514 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92514 is an use after free vulnerability in Linux, published on 17 Sep 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-92514 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-92514/ (Markdown: https://insights.sbomify.com/CVE-2026-92514/index.md)
```

## Sources

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

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