CVE-2025-21665: filemap: avoid truncating 64-bit offset to 32 bits
In the Linux kernel, the following vulnerability has been resolved:
filemap: avoid truncating 64-bit offset to 32 bits
On 32-bit kernels, folio_seek_hole_data() was inadvertently truncating a
64-bit value to 32 bits, leading to a possible infinite loop when writing
to an xfs filesystem.
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can let a local low-privileged user cause an affected 32-bit system using XFS to hang in an infinite loop. The business impact is availability, not data theft or tampering. It matters most for shared servers, appliances, or legacy 32-bit deployments where untrusted users or workloads can write to XFS filesystems.
Executive priority
Treat as a targeted availability risk, not a broad remote compromise issue. Patch during normal security maintenance, but accelerate on shared 32-bit XFS systems where local users or workloads are not fully trusted.
Technical view
On 32-bit kernels, folio_seek_hole_data() truncates a 64-bit offset to 32 bits. The CVE states this can create an infinite loop when writing to an XFS filesystem. CVSS is 5.5 with local access, low complexity, low privileges, no user interaction, and high availability impact only.
Likely exposure
Exposure appears limited to affected Linux kernel builds on 32-bit systems, especially those using XFS. Internet-facing exposure is not indicated by the sources because the attack vector is local. Cloud, container, and appliance risk depends on whether tenants or local users can write to an affected host filesystem.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. The documented path is local denial of service through the kernel filesystem behavior. Sources do not provide exploit details, public weaponization evidence, or remote attack claims.
Researcher notes
Evidence supports CWE-835 infinite loop caused by integer truncation in folio_seek_hole_data() on 32-bit kernels. The CVE references multiple Linux stable commits and a Debian LTS advisory. The bundle does not provide complete product-specific package versions across all distributions.
Mitigation direction
Apply Linux stable or distribution kernel updates that include the referenced fixes.
Prioritize 32-bit systems, shared hosts, and systems using XFS.
Use distribution security advisories when vendor kernels backport fixes without changing major versions.
If no package is available, track vendor guidance for CVE-2025-21665.
Reduce local untrusted write access to affected XFS filesystems where practical.
Validation and detection
Inventory Linux hosts for 32-bit kernels and XFS filesystem usage.
Check vendor advisories or package changelogs for CVE-2025-21665.
Confirm the running kernel includes the relevant stable fix or vendor backport.
Validate reboot completion where kernel package installation requires it.
Review monitoring for unexplained hangs on affected legacy systems.
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-835: 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-835 · source CWE mapping
Loop with Unreachable Exit Condition ('Infinite Loop')
Loop with Unreachable Exit Condition ('Infinite Loop') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.