| 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-21736: nilfs2: fix possible int overflows in nilfs_fiemap() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| nilfs2: fix possible int overflows in nilfs_fiemap() |
| |
| Since nilfs_bmap_lookup_contig() in nilfs_fiemap() calculates its result |
| by being prepared to go through potentially maxblocks == INT_MAX blocks, |
| the value in n may experience an overflow caused by left shift of blkbits. |
| |
| While it is extremely unlikely to occur, play it safe and cast right hand |
| expression to wider type to mitigate the issue. |
| |
| Found by Linux Verification Center (linuxtesting.org) with static analysis |
| tool SVACE. |
| |
| The Linux kernel CVE team has assigned CVE-2025-21736 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 2.6.38 with commit 622daaff0a8975fb5c5b95f24f3234550ba32e92 and fixed in 5.4.291 with commit 7649937987fed51ed09985da4019d50189fc534e |
| Issue introduced in 2.6.38 with commit 622daaff0a8975fb5c5b95f24f3234550ba32e92 and fixed in 5.10.235 with commit 58b1c6881081f5ddfb9a14dc241a74732c0f855c |
| Issue introduced in 2.6.38 with commit 622daaff0a8975fb5c5b95f24f3234550ba32e92 and fixed in 5.15.179 with commit 8f41df5fd4c11d26e929a85f7239799641f92da7 |
| Issue introduced in 2.6.38 with commit 622daaff0a8975fb5c5b95f24f3234550ba32e92 and fixed in 6.1.129 with commit f3d80f34f58445355fa27b9579a449fb186aa64e |
| Issue introduced in 2.6.38 with commit 622daaff0a8975fb5c5b95f24f3234550ba32e92 and fixed in 6.6.78 with commit f2bd0f1ab47822fe5bd699c8458b896c4b2edea1 |
| Issue introduced in 2.6.38 with commit 622daaff0a8975fb5c5b95f24f3234550ba32e92 and fixed in 6.12.14 with commit b9495a9109abc31d3170f7aad7d48aa64610a1a2 |
| Issue introduced in 2.6.38 with commit 622daaff0a8975fb5c5b95f24f3234550ba32e92 and fixed in 6.13.3 with commit 250423300b4b0335918be187ef3cade248c06e6a |
| Issue introduced in 2.6.38 with commit 622daaff0a8975fb5c5b95f24f3234550ba32e92 and fixed in 6.14 with commit 6438ef381c183444f7f9d1de18f22661cba1e946 |
| |
| 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-21736 |
| 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/nilfs2/inode.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/7649937987fed51ed09985da4019d50189fc534e |
| https://git.kernel.org/stable/c/58b1c6881081f5ddfb9a14dc241a74732c0f855c |
| https://git.kernel.org/stable/c/8f41df5fd4c11d26e929a85f7239799641f92da7 |
| https://git.kernel.org/stable/c/f3d80f34f58445355fa27b9579a449fb186aa64e |
| https://git.kernel.org/stable/c/f2bd0f1ab47822fe5bd699c8458b896c4b2edea1 |
| https://git.kernel.org/stable/c/b9495a9109abc31d3170f7aad7d48aa64610a1a2 |
| https://git.kernel.org/stable/c/250423300b4b0335918be187ef3cade248c06e6a |
| https://git.kernel.org/stable/c/6438ef381c183444f7f9d1de18f22661cba1e946 |
