CVE-2025-21667: iomap: avoid avoid truncating 64-bit offset to 32 bits
In the Linux kernel, the following vulnerability has been resolved:
iomap: avoid avoid truncating 64-bit offset to 32 bits
on 32-bit kernels, iomap_write_delalloc_scan() was inadvertently using a
32-bit position due to folio_next_index() returning an unsigned long.
This could lead to an infinite loop when writing to an xfs filesystem.
Security readout for executives and security teams
Plain-English summary
CVE-2025-21667 is a Linux kernel availability bug. On some 32-bit systems using XFS, a write operation can hit an infinite loop in kernel filesystem code. The practical concern is service disruption or a hung workload, not data theft or privilege escalation based on the provided sources.
Executive priority
Treat this as a targeted availability risk. It is not a broad remote emergency, but affected 32-bit XFS systems running critical workloads should be updated promptly because a local trigger can cause serious service disruption.
Technical view
The bug is in Linux iomap delayed-allocation scanning. On 32-bit kernels, folio_next_index() returns unsigned long, which can truncate a 64-bit file offset to 32 bits. During XFS writes this can cause iomap_write_delalloc_scan() to loop indefinitely. CVSS is 5.5, local, low complexity, low privilege, availability-only impact.
Likely exposure
Exposure is most likely on 32-bit Linux kernels using XFS where local users or workloads can perform writes. The source bundle lists Linux kernel branches and stable commits, but distribution-specific package mapping must be checked against each vendor advisory.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector indicates local access with low privileges and no user interaction. Evidence supports a denial-of-service scenario rather than remote compromise.
Researcher notes
The key condition is 64-bit offset truncation on 32-bit kernels in iomap_write_delalloc_scan(). Validate exposure through architecture, filesystem, and kernel lineage rather than product name alone. The affected-version evidence is kernel-centric and may require distribution backport review.
Mitigation direction
Apply vendor kernel updates containing the referenced stable fixes.
Prioritize 32-bit Linux systems using XFS filesystems.
Check Debian LTS guidance if running affected Debian kernel packages.
If patching is delayed, reduce untrusted local write access on exposed hosts.
Schedule reboot or kernel live-patch validation after updating.
Validation and detection
Inventory Linux hosts for 32-bit kernels and XFS usage.
Map installed kernel packages to vendor advisories for CVE-2025-21667.
Confirm the running kernel includes the applicable stable fix.
Verify updated hosts have rebooted into the fixed kernel.
Review monitoring for filesystem write hangs or kernel availability symptoms.
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.