| 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: <2025081913-CVE-2025-38579-db94@gregkh> Date: Tue, 19 Aug 2025 19:18:25 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-38579: f2fs: fix KMSAN uninit-value in extent_info usage From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: f2fs: fix KMSAN uninit-value in extent_info usage KMSAN reported a use of uninitialized value in `__is_extent_mergeable()` and `__is_back_mergeable()` via the read extent tree path. The root cause is that `get_read_extent_info()` only initializes three fields (`fofs`, `blk`, `len`) of `struct extent_info`, leaving the remaining fields uninitialized. This leads to undefined behavior when those fields are accessed later, especially during extent merging. Fix it by zero-initializing the `extent_info` struct before population. The Linux kernel CVE team has assigned CVE-2025-38579 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit 94afd6d6e5253179c9b891d02081cc8355a11768 and fixed in 6.1.148 with commit e68b751ec2b15d866967812c57cfdfc1eba6a269 Issue introduced in 5.15 with commit 94afd6d6e5253179c9b891d02081cc8355a11768 and fixed in 6.6.102 with commit dabfa3952c8e6bfe6414dbf32e8b6c5f349dc898 Issue introduced in 5.15 with commit 94afd6d6e5253179c9b891d02081cc8355a11768 and fixed in 6.12.42 with commit 44a79437309e0ee2276ac17aaedc71253af253a8 Issue introduced in 5.15 with commit 94afd6d6e5253179c9b891d02081cc8355a11768 and fixed in 6.15.10 with commit cc1615d5aba4f396cf412579928539a2b124c8a0 Issue introduced in 5.15 with commit 94afd6d6e5253179c9b891d02081cc8355a11768 and fixed in 6.16.1 with commit 01b6f5955e0008af6bc3a181310d2744bb349800 Issue introduced in 5.15 with commit 94afd6d6e5253179c9b891d02081cc8355a11768 and fixed in 6.17-rc1 with commit 154467f4ad033473e5c903a03e7b9bca7df9a0fa 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-38579 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/f2fs/extent_cache.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/e68b751ec2b15d866967812c57cfdfc1eba6a269 https://git.kernel.org/stable/c/dabfa3952c8e6bfe6414dbf32e8b6c5f349dc898 https://git.kernel.org/stable/c/44a79437309e0ee2276ac17aaedc71253af253a8 https://git.kernel.org/stable/c/cc1615d5aba4f396cf412579928539a2b124c8a0 https://git.kernel.org/stable/c/01b6f5955e0008af6bc3a181310d2744bb349800 https://git.kernel.org/stable/c/154467f4ad033473e5c903a03e7b9bca7df9a0fa
Powered by blists - more mailing lists