# CVE-2026-80729: mm/huge_memory: initialise workingset state before folio split

> A missing initialization in the Linux kernel memory management subsystem can cause a kernel warning and potential denial of service during memory reclaim.

- **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:** 3 Sep 2026
- **Updated:** 11 Oct 2026
- **Also known as:** BELL-CVE-2026-80729, DEBIAN-CVE-2026-80729, GHSA-p2p8-6fmx-rfj9, UBUNTU-CVE-2026-80729

## What is CVE-2026-80729?

CVE-2026-80729 is a vulnerability in Linux, published on 3 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:

mm/huge_memory: initialise workingset state before folio split

xas_try_split() adds __GFP_ACCOUNT for page-cache xa_nodes, but
__folio_split() leaves the xa_state's xa_lru unset.  That lets a live,
memcg-charged xa_node exist without being linked into the mapping's
shadow_nodes list_lru; when reclaim later walks the list_lru it trips
VM_WARN_ON(!css_is_dying()).

Use mapping_set_update() to install both the workingset update callback
and the shadow_nodes list_lru on the xa_state.

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


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

Apply the vendor's patch.

## Is CVE-2026-80729 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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