# CVE-2026-97413: RDMA/rtrs-srv: Fix integer underflow in process_read and process_write

> A malicious RDMA client can trigger an integer underflow in the Linux kernel, leading to out-of-bounds memory access and potential code execution or denial of service.

- **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:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103829, BELL-CVE-2026-97413, DEBIAN-CVE-2026-97413, GHSA-wv45-qhgq-9h5f, UBUNTU-CVE-2026-97413

## What is CVE-2026-97413?

CVE-2026-97413 is a critical vulnerability in Linux, published on 24 Sep 2026. 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/rtrs-srv: Fix integer underflow in process_read and process_write

usr_len is read from a network-supplied message field (le16_to_cpu)
and used to compute data_len = off - usr_len without validating that
usr_len <= off. A malicious RDMA client can send usr_len > off causing
an integer underflow, resulting in data_len wrapping to a huge size_t
value which is then passed to the rdma_ev callback as a memory length,
leading to out-of-bounds memory access.

Fix by reading and validating usr_len <= off before rtrs_srv_get_ops_ids()
in both process_read() and process_write(), ensuring the early return
path acquires no reference and has no resource leak.

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


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

Apply the vendor's patch.

## Is CVE-2026-97413 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97413 is a critical vulnerability in Linux, published on 24 Sep 2026. 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-2026-97413 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-97413/ (Markdown: https://insights.sbomify.com/CVE-2026-97413/index.md)
```

## Sources

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

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