| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-21667: iomap: avoid avoid truncating 64-bit offset to 32 bits |
| |
| Description |
| =========== |
| |
| 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. |
| |
| The Linux kernel CVE team has assigned CVE-2025-21667 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.1.92 with commit 38be53c3fd7f4f4bd5de319a323d72f9f6beb16d and fixed in 6.1.127 with commit 7ca4bd6b754913910151acce00be093f03642725 |
| Issue introduced in 6.2 with commit f43dc4dc3eff028b5ddddd99f3a66c5a6bdd4e78 and fixed in 6.6.74 with commit 91371922704c8d82049ef7c2ad974d0a2cd1174d |
| Issue introduced in 6.2 with commit f43dc4dc3eff028b5ddddd99f3a66c5a6bdd4e78 and fixed in 6.12.11 with commit 402ce16421477e27f30b57d6d1a6dc248fa3a4e4 |
| Issue introduced in 6.2 with commit f43dc4dc3eff028b5ddddd99f3a66c5a6bdd4e78 and fixed in 6.13 with commit c13094b894de289514d84b8db56d1f2931a0bade |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2025-21667 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| fs/iomap/buffered-io.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/7ca4bd6b754913910151acce00be093f03642725 |
| https://git.kernel.org/stable/c/91371922704c8d82049ef7c2ad974d0a2cd1174d |
| https://git.kernel.org/stable/c/402ce16421477e27f30b57d6d1a6dc248fa3a4e4 |
| https://git.kernel.org/stable/c/c13094b894de289514d84b8db56d1f2931a0bade |
