# CVE-2026-68086: mm/khugepaged: write all dirty file folios when collapsing


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** AZL-95058, BELL-CVE-2026-68086, DEBIAN-CVE-2026-68086, GHSA-f6v6-h22p-v3m3, UBUNTU-CVE-2026-68086

## What is CVE-2026-68086?

CVE-2026-68086 is a vulnerability in Linux, published on 10 Aug 2026. 

### Official description

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

mm/khugepaged: write all dirty file folios when collapsing

[There is no upstream commit, as this code was removed by upstream
 commit 044925f9b565 ("mm: fs: remove filemap_nr_thps*() functions and their users")]

As-is, khugepaged and writable-file opening exclude each other. A file
cannot be open writeable and have THPs (because the filesystem is not aware
of them). khugepaged will never collapse file pages for files that are
opened writeable. On an open(O_RDWR/O_WRONLY), the page cache for that
particular file is dropped. This is fine because nothing could've been
dirtied.

However, there is an edge-case: collapse_file() might not be able to
coexist with concurrent writers, but it can coexist with dirty folios
(from previous writers). Therefore, the following can happen:

open(file, O_RDWR)
write(file)
close(file)
madvise(file_mapping, MADV_COLLAPSE, some non-dirty range)
open(file, O_RDWR)
 nr_thps > 0
  truncate_inode_pages()
    /* THPs are cleared out, but so are the dirty folios */

When this edge-case happens, there is data loss, as the dirty folios are
fully discarded.

Fix it by fully writing back the page cache (and waiting) when collapsing
file THPs. Doing so provides the guarantee that no dirty folio will be
observed while there are active THPs. To fully ensure this is safe, the
invalidate_lock needs to be held while doing the writeout, so that
do_dentry_open()'s page cache truncation excludes this write-and-wait.

As a side effect, move the nr_thps counter bumping outside the i_pages
lock. This is correct since the counter itself is an atomic_t and the
producer <-> consumer correctness is provided by a full memory barrier:
smp_mb() in collapse_file()/memory barrier implied by full ordering in
get_write_access() -> atomic_inc_unless_negative().

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


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

Upgrade to a fixed version.

## Is CVE-2026-68086 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68086 is a vulnerability in Linux, published on 10 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-68086 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-68086/ (Markdown: https://insights.sbomify.com/CVE-2026-68086/index.md)
```

## Sources

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

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