CVE-2025-22000: mm/huge_memory: drop beyond-EOF folios with the right number of refs
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-22000 is a Linux kernel memory leak in huge memory handling during file truncation. A local user could trigger conditions that fail to free cached memory, potentially reducing system availability. It does not affect confidentiality or integrity according to the CVSS vector.
Executive priority
Treat as a routine but important availability fix. Prioritize shared Linux servers, multi-tenant systems, and environments running untrusted local workloads. This is not currently evidenced as remotely exploitable or actively exploited.
Technical view
The bug is in mm/huge_memory. After a folio split, large beyond-EOF folios may be dropped with too few references, leaving page-cache references behind. This can leak memory on filesystems with block size greater than page size when truncate causes folios to split into nonzero-order folios.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions and using filesystem conditions described by the kernel notice. The issue requires local access with low privileges. Internet-facing remote exploitation is not indicated by the provided sources.
Exploitation context
The CVSS vector is local, low complexity, low privilege, no user interaction, with high availability impact. CISA KEV is false in the provided data, and no cited source states active exploitation.
Researcher notes
Evidence is limited to the CVE record and Linux stable commits. The vulnerable condition is specific: truncate on filesystems with blocksize greater than page size causing split folios above order zero. Do not assume all Linux deployments are practically exposed without confirming filesystem and kernel details.
Mitigation direction
Review Linux vendor advisories for your distribution and kernel branch.
Update to a kernel release containing the referenced stable fixes.
Prioritize systems allowing local users or untrusted workloads.
If patching is delayed, monitor memory pressure on affected hosts.
Validation and detection
Inventory Linux kernel versions across servers and workloads.
Compare running kernels against vendor advisories for CVE-2025-22000.
Check whether referenced stable commits are included in your kernel build.
Identify systems using filesystems with block size greater than page size.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.