| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025111243-CVE-2025-40179-6d22@gregkh> Date: Wed, 12 Nov 2025 17:00:42 -0500 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-40179: ext4: verify orphan file size is not too big From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: ext4: verify orphan file size is not too big In principle orphan file can be arbitrarily large. However orphan replay needs to traverse it all and we also pin all its buffers in memory. Thus filesystems with absurdly large orphan files can lead to big amounts of memory consumed. Limit orphan file size to a sane value and also use kvmalloc() for allocating array of block descriptor structures to avoid large order allocations for sane but large orphan files. The Linux kernel CVE team has assigned CVE-2025-40179 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit 02f310fcf47fa9311d6ba2946a8d19e7d7d11f37 and fixed in 5.15.195 with commit 95a21611b14ae0a401720645245a8db16f040995 Issue introduced in 5.15 with commit 02f310fcf47fa9311d6ba2946a8d19e7d7d11f37 and fixed in 6.1.157 with commit 566a1d6084563bd07433025aa23bcea4427de107 Issue introduced in 5.15 with commit 02f310fcf47fa9311d6ba2946a8d19e7d7d11f37 and fixed in 6.6.113 with commit 304fc34ff6fc8261138fd81f119e024ac3a129e9 Issue introduced in 5.15 with commit 02f310fcf47fa9311d6ba2946a8d19e7d7d11f37 and fixed in 6.12.54 with commit a2d803fab8a6c6a874277cb80156dc114db91921 Issue introduced in 5.15 with commit 02f310fcf47fa9311d6ba2946a8d19e7d7d11f37 and fixed in 6.17.4 with commit 2b9da798ff0f4d026c5f0f815047393ebe7d8859 Issue introduced in 5.15 with commit 02f310fcf47fa9311d6ba2946a8d19e7d7d11f37 and fixed in 6.18-rc1 with commit 0a6ce20c156442a4ce2a404747bb0fb05d54eeb3 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-40179 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/ext4/orphan.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/95a21611b14ae0a401720645245a8db16f040995 https://git.kernel.org/stable/c/566a1d6084563bd07433025aa23bcea4427de107 https://git.kernel.org/stable/c/304fc34ff6fc8261138fd81f119e024ac3a129e9 https://git.kernel.org/stable/c/a2d803fab8a6c6a874277cb80156dc114db91921 https://git.kernel.org/stable/c/2b9da798ff0f4d026c5f0f815047393ebe7d8859 https://git.kernel.org/stable/c/0a6ce20c156442a4ce2a404747bb0fb05d54eeb3
Powered by blists - more mailing lists