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, iomapwritedelallocscan() was inadvertently using a 32-bit position due to folionextindex() returning an unsigned long. This could lead to an infinite loop when writing to an xfs filesystem.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.76.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-21667?
CVE-2025-21667 is categorized as a medium severity vulnerability due to the potential for infinite loops caused by 32-bit offset truncation on 32-bit kernels.
How do I fix CVE-2025-21667?
To fix CVE-2025-21667, update your Linux kernel to a version newer than 6.1.127 or ensure you are using a fixed version that does not have this vulnerability.
What versions of the Linux kernel are affected by CVE-2025-21667?
CVE-2025-21667 affects 32-bit kernels within specified version ranges prior to patches included in updated releases.
When was CVE-2025-21667 disclosed?
CVE-2025-21667 was disclosed as part of the continuous security updates for the Linux kernel.
What are the potential impacts of CVE-2025-21667?
The potential impacts of CVE-2025-21667 include system instability and potential infinite loops in processes that utilize the affected iomap functionality.