# CVE-2026-90292: RDMA/siw: Fix use-after-free in siw_accept()

> A use-after-free in the Linux kernel's RDMA/siw module allows attackers to execute arbitrary code or escalate privileges via crafted user-space requests.

- **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-101888, BELL-CVE-2026-90292, DEBIAN-CVE-2026-90292, GHSA-8qxc-hwhr-6xrv, UBUNTU-CVE-2026-90292

## What is CVE-2026-90292?

CVE-2026-90292 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/siw: Fix use-after-free in siw_accept()

siw_accept() looks up the QP supplied by userspace. If that QP is
already in RTS, the function jumps to error cleanup before associating
the incoming CEP with it.

The cleanup tests whether qp->cep is non-NULL and assumes the current
call installed the association. However, qp->cep can point to the CEP
of an existing connection. The cleanup then drops a reference from the
incoming cep, not qp->cep. Once the incoming endpoint loses its
remaining references, this can free it before the subsequent cep->qp
store, causing a use-after-free. It also clears the existing QP
association.

Only release the association reference when qp->cep is the incoming
CEP. This preserves an existing association and avoids accessing the
freed endpoint.

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


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

Apply the vendor's patch.

## Is CVE-2026-90292 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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