# CVE-2026-92508: RDMA/core: Fix potential use after free in ib_free_cq()

> A use-after-free vulnerability in the Linux kernel RDMA core allows attackers to potentially execute code or escalate privileges via the netlink path.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-102609, BELL-CVE-2026-92508, DEBIAN-CVE-2026-92508, GHSA-mfv8-fqx8-q27x, UBUNTU-CVE-2026-92508

## What is CVE-2026-92508?

CVE-2026-92508 is a high-severity 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/core: Fix potential use after free in ib_free_cq()

When accessing a CQ via the netlink path the only synchronization
mechanism for the said CQ is rdma_restrack_get().
Currently, rdma_restrack_del() is invoked at the end of
ib_free_cq(), which is too late, since by that point
vendor-specific resources associated with the CQ might already be
freed. This can leave a short window where the CQ remains accessible
through restrack, leading to a potential use-after-free.

Fix this by moving the rdma_restrack_del() call to be before the freeing
of the vendor-specific resources ensuring that the CQ is removed from
restrack before its internal resources are released.
This guarantees that no new users hold references to a CQ that is in
the process of destruction.

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


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

Apply the vendor's patch.

## Is CVE-2026-92508 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92508 is a high-severity 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-92508 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-92508/ (Markdown: https://insights.sbomify.com/CVE-2026-92508/index.md)
```

## Sources

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

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