# CVE-2026-80898: netfs: clear PG_private_2 on copy-to-cache append failure

> A bug in the Linux kernel netfs module fails to clear a page flag on append failure, potentially leading to resource leaks or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** BELL-CVE-2026-80898, DEBIAN-CVE-2026-80898, GHSA-rr37-5j55-39mh, UBUNTU-CVE-2026-80898

## What is CVE-2026-80898?

CVE-2026-80898 is a vulnerability in Linux, published on 4 Sep 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:

netfs: clear PG_private_2 on copy-to-cache append failure

netfs_pgpriv2_copy_to_cache() marks the folio with PG_private_2 before
netfs_pgpriv2_copy_folio() appends it to the copy-to-cache rolling
buffer.

If the append fails, the folio is not queued for cache writeback, so
the PG_private_2 state and its reference must be released immediately.

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


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

Apply the vendor's patch.

## Is CVE-2026-80898 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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