# CVE-2026-80571: powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak

> A buffer overflow in the Linux kernel's powerpc/pseries papr-phy-attest driver allows local attackers to execute code or escalate privileges due to missing length validation.

- **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:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** BELL-CVE-2026-80571, DEBIAN-CVE-2026-80571, UBUNTU-CVE-2026-80571

## What is CVE-2026-80571?

CVE-2026-80571 is a memory corruption vulnerability in Linux, published on 26 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:

powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak

In papr_phy_attest_create_handle(), the params->cmd.length is not
validated before use, which can result in a buffer overlow.  Check it and
return -EINVAL if it is either 0 or exceeds sizeof(params->cmd).

Also, params is freed on the success path but not error. Free it on
errors after memory allocation.  And free it on negative fd.

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


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

Apply the vendor's patch.

## Is CVE-2026-80571 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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