# RDMA/rxe: Fix mr leak in RESPST_ERR_RNR

CVE record · `CVE-2022-49929`

- **Identifiers:** `CVE-2022-49929`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 May 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 May 2025, 14:11 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `8a1a0be894da0d06bfbb496cc2dc3057fa83e103 to before 50b35ad2864a9d66f802f9ce193d99bbef64e219` (git)
  - affected: `8a1a0be894da0d06bfbb496cc2dc3057fa83e103 to before b5f9a01fae42684648c2ee3cd9985f80c67ab9f7` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.18`
  - unaffected: `before 5.18` (semver)
  - unaffected: `6.0.8 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel 5.18 is affected by a memory region reference leak in the RDMA rxe driver's RESPST_ERR_RNR path, which triggers a kernel warning during cleanup. The source gives few details on what an attacker would need or could do. Upgrade to Linux 6.0.8 or later in the 6.0 series, or to 6.1 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0016, the 5th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 May 2025, 14:11 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49929)
- 1 May 2025, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49929)

## Sources

- [CVE List: CVE-2022-49929](https://www.cve.org/CVERecord?id=CVE-2022-49929)
- [NVD: CVE-2022-49929](https://nvd.nist.gov/vuln/detail/CVE-2022-49929)

### References from the CNA

- <https://git.kernel.org/stable/c/50b35ad2864a9d66f802f9ce193d99bbef64e219>
- <https://git.kernel.org/stable/c/b5f9a01fae42684648c2ee3cd9985f80c67ab9f7>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-49929>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-49929/>. Everything for agents: <https://agentprime.io/llms.txt>.
