# CVE-2026-74345: RDMA/siw: Fix endpoint/socket association handling

> A use-after-free vulnerability in the Linux kernel's RDMA/siw driver allows attackers to cause a denial of service or potentially execute code via malformed MPA requests.

- **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:** 21 Oct 2026
- **Also known as:** AZL-96228, BELL-CVE-2026-74345, DEBIAN-CVE-2026-74345, GHSA-qccr-c782-7qrw, UBUNTU-CVE-2026-74345

## What is CVE-2026-74345?

CVE-2026-74345 is a critical use after free 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/siw: Fix endpoint/socket association handling

Disassociating a socket from an endpoint via siw_socket_disassoc() may
release the last reference on that endpoint and free it. Therefore, don't
clear the endpoints socket pointer after calling that function, but
within.

This fixes a:

  BUG: KASAN: slab-use-after-free in siw_cm_work_handler (drivers/infiniband/sw/siw/siw_cm.c:1053 drivers/infiniband/sw/siw/siw_cm.c:1075)

which occurred after processing a malformed MPA request during connection
establishment, causing the new endpoint to be closed.

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


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

Apply the vendor's patch.

## Is CVE-2026-74345 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74345 is a critical use after free 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-74345 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-74345/ (Markdown: https://insights.sbomify.com/CVE-2026-74345/index.md)
```

## Sources

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

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