# CVE-2022-50666: RDMA/siw: Fix QP destroy to wait for all references dropped.

> A use-after-free in the Linux kernel RDMA subsystem allows attackers to cause denial of service or execute code via delayed connection handling.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2022-50666, GHSA-mppj-wh3r-grwx, ROOT-OS-DEBIAN-11-CVE-2022-50666, UBUNTU-CVE-2022-50666

## What is CVE-2022-50666?

CVE-2022-50666 is a critical use after free vulnerability in Linux, published on 9 Dec 2025. 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/siw: Fix QP destroy to wait for all references dropped.

Delay QP destroy completion until all siw references to QP are
dropped. The calling RDMA core will free QP structure after
successful return from siw_qp_destroy() call, so siw must not
hold any remaining reference to the QP upon return.
A use-after-free was encountered in xfstest generic/460, while
testing NFSoRDMA. Here, after a TCP connection drop by peer,
the triggered siw_cm_work_handler got delayed until after
QP destroy call, referencing a QP which has already freed.

## Which versions are affected by CVE-2022-50666?


## How do I fix CVE-2022-50666?

Apply the vendor's patch.

## Is CVE-2022-50666 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50666 and fix it if it is affected.

What it is: CVE-2022-50666 is a critical use after free vulnerability in Linux, published on 9 Dec 2025. 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-2022-50666 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-2022-50666/ (Markdown: https://insights.sbomify.com/CVE-2022-50666/index.md)
```

## Sources

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

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