# CVE-2026-72150: sunrpc: fix uninitialized xprt_create_args structure

> A local attacker can trigger a kernel panic or leak sensitive stack data due to uninitialized memory in the sunrpc subsystem.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** BELL-CVE-2026-72150, DEBIAN-CVE-2026-72150, GHSA-3r6v-v38p-c2r8, UBUNTU-CVE-2026-72150

## What is CVE-2026-72150?

CVE-2026-72150 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

sunrpc: fix uninitialized xprt_create_args structure

The xprt_create_args structure is allocated on the stack without
initialization in rpc_sysfs_xprt_switch_add_xprt_store(). While some
fields are manually populated, critical fields like srcaddr, bc_xps,
and flags contain uninitialized stack garbage.

This can lead to:
1. Kernel panic when xs_setup_xprt() dereferences garbage srcaddr
2. Information leak if srcaddr points to sensitive stack data
3. Unpredictable behavior if flags has random bits set

The fix is to zero-initialize the structure to ensure all unused
fields are NULL/0, preventing the transport setup code from acting
on garbage data.

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


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

Apply the vendor's patch.

## Is CVE-2026-72150 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72150 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72150 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-72150/ (Markdown: https://insights.sbomify.com/CVE-2026-72150/index.md)
```

## Sources

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

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