| 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: <2025111246-CVE-2025-40198-7a99@gregkh> Date: Wed, 12 Nov 2025 17:01:01 -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-40198: ext4: avoid potential buffer over-read in parse_apply_sb_mount_options() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: ext4: avoid potential buffer over-read in parse_apply_sb_mount_options() Unlike other strings in the ext4 superblock, we rely on tune2fs to make sure s_mount_opts is NUL terminated. Harden parse_apply_sb_mount_options() by treating s_mount_opts as a potential __nonstring. The Linux kernel CVE team has assigned CVE-2025-40198 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.36 with commit 8b67f04ab9de5d8f3a71aef72bf02c995a506db5 and fixed in 5.4.301 with commit 7bf46ff83a0ef11836e38ebd72cdc5107209342d Issue introduced in 2.6.36 with commit 8b67f04ab9de5d8f3a71aef72bf02c995a506db5 and fixed in 5.10.246 with commit b2bac84fde28fb6a88817b8b761abda17a1d300b Issue introduced in 2.6.36 with commit 8b67f04ab9de5d8f3a71aef72bf02c995a506db5 and fixed in 6.1.158 with commit e651294218d2684302ee5ed95ccf381646f3e5b4 Issue introduced in 2.6.36 with commit 8b67f04ab9de5d8f3a71aef72bf02c995a506db5 and fixed in 6.6.114 with commit 01829af7656b56d83682b3491265d583d502e502 Issue introduced in 2.6.36 with commit 8b67f04ab9de5d8f3a71aef72bf02c995a506db5 and fixed in 6.12.54 with commit 2a0cf438320cdb783e0378570744c0ef0d83e934 Issue introduced in 2.6.36 with commit 8b67f04ab9de5d8f3a71aef72bf02c995a506db5 and fixed in 6.17.4 with commit a6e94557cd05adc82fae0400f6e17745563e5412 Issue introduced in 2.6.36 with commit 8b67f04ab9de5d8f3a71aef72bf02c995a506db5 and fixed in 6.18-rc1 with commit 8ecb790ea8c3fc69e77bace57f14cf0d7c177bd8 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-40198 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/super.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/7bf46ff83a0ef11836e38ebd72cdc5107209342d https://git.kernel.org/stable/c/b2bac84fde28fb6a88817b8b761abda17a1d300b https://git.kernel.org/stable/c/e651294218d2684302ee5ed95ccf381646f3e5b4 https://git.kernel.org/stable/c/01829af7656b56d83682b3491265d583d502e502 https://git.kernel.org/stable/c/2a0cf438320cdb783e0378570744c0ef0d83e934 https://git.kernel.org/stable/c/a6e94557cd05adc82fae0400f6e17745563e5412 https://git.kernel.org/stable/c/8ecb790ea8c3fc69e77bace57f14cf0d7c177bd8
Powered by blists - more mailing lists