# CVE-2025-22000: mm/huge_memory: drop beyond-EOF folios with the right number of refs

> A memory leak in the Linux kernel huge memory subsystem can cause resource exhaustion and denial of service when truncating files on filesystems with block sizes larger than page size.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 3 Apr 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-22000, DEBIAN-CVE-2025-22000, GHSA-84gc-cf68-frm5, UBUNTU-CVE-2025-22000

## What is CVE-2025-22000?

CVE-2025-22000 is a medium-severity denial of service vulnerability in Linux kernel, published on 3 Apr 2025. 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: drop beyond-EOF folios with the right number of refs

When an after-split folio is large and needs to be dropped due to EOF,
folio_put_refs(folio, folio_nr_pages(folio)) should be used to drop all
page cache refs.  Otherwise, the folio will not be freed, causing memory
leak.

This leak would happen on a filesystem with blocksize > page_size and a
truncate is performed, where the blocksize makes folios split to >0 order
ones, causing truncated folios not being freed.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2025-22000?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-22000?

Apply the vendor's patch.

## Is CVE-2025-22000 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22000 and fix it if it is affected.

What it is: CVE-2025-22000 is a medium-severity denial of service vulnerability in Linux kernel, published on 3 Apr 2025. 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-2025-22000 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2025-22000/ (Markdown: https://insights.sbomify.com/CVE-2025-22000/index.md)
```

## Sources

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

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