# CVE-2026-74394: RDMA/srpt: fix integer overflow in immediate data length check

> A malicious network initiator can trigger an integer overflow in the Linux kernel RDMA subsystem, potentially leading to memory corruption 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:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74394, DEBIAN-CVE-2026-74394, GHSA-f87m-vg23-g294, UBUNTU-CVE-2026-74394

## What is CVE-2026-74394?

CVE-2026-74394 is a critical vulnerability in Linux, published on 15 Aug 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/srpt: fix integer overflow in immediate data length check

imm_buf->len is a user-controlled uint32_t received from the network.
Adding it to imm_data_offset without overflow checking allows a
malicious initiator to send len=0xFFFFFFFF, causing req_size to wrap
around to a small value, bypassing the bounds check, and subsequently
passing a ~4GB length to sg_init_one().

Use check_add_overflow() to detect wrapping before the comparison.

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


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

Apply the vendor's patch.

## Is CVE-2026-74394 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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