# CVE-2022-50736: RDMA/siw: Fix immediate work request flush to completion queue

> A local attacker can trigger an out-of-bounds access in the Linux kernel RDMA subsystem, potentially causing a crash or executing arbitrary code.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 24 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-50736, GHSA-p4wh-wgxj-q3c5, UBUNTU-CVE-2022-50736

## What is CVE-2022-50736?

CVE-2022-50736 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 2025. 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 immediate work request flush to completion queue

Correctly set send queue element opcode during immediate work request
flushing in post sendqueue operation, if the QP is in ERROR state.
An undefined ocode value results in out-of-bounds access to an array
for mapping the opcode between siw internal and RDMA core representation
in work completion generation. It resulted in a KASAN BUG report
of type 'global-out-of-bounds' during NFSoRDMA testing.

This patch further fixes a potential case of a malicious user which may
write undefined values for completion queue elements status or opcode,
if the CQ is memory mapped to user land. It avoids the same out-of-bounds
access to arrays for status and opcode mapping as described above.

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


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

Apply the vendor's patch.

## Is CVE-2022-50736 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50736 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 2025. 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-2022-50736 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-50736/ (Markdown: https://insights.sbomify.com/CVE-2022-50736/index.md)
```

## Sources

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

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