# CVE-2026-74432: rxrpc: Fix leak of released call in recvmsg(MSG_PEEK)

> A local attacker can cause a memory leak in the Linux kernel's rxrpc module via recvmsg with MSG_PEEK, leading to resource exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** BELL-CVE-2026-74432, DEBIAN-CVE-2026-74432, GHSA-mhvf-j96m-638q, UBUNTU-CVE-2026-74432

## What is CVE-2026-74432?

CVE-2026-74432 is a denial of service vulnerability in Linux, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

rxrpc: Fix leak of released call in recvmsg(MSG_PEEK)

Fix rxrpc_recvmsg() to also drop the ref it holds on an already-released
call if MSG_PEEK is in force (the function holds a ref on the call
irrespective of whether MSG_PEEK is specified or not).

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


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

Apply the vendor's patch.

## Is CVE-2026-74432 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74432 is a denial of service vulnerability in Linux, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74432 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-74432/ (Markdown: https://insights.sbomify.com/CVE-2026-74432/index.md)
```

## Sources

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

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