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: <2025050220-CVE-2023-53091-9433@gregkh> Date: Fri, 2 May 2025 17:55:56 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-53091: ext4: update s_journal_inum if it changes after journal replay From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: ext4: update s_journal_inum if it changes after journal replay When mounting a crafted ext4 image, s_journal_inum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the journal through the old s_journal_inum. And the new s_journal_inum bypasses some of the checks in ext4_get_journal(), which may trigger a null pointer dereference problem. So if s_journal_inum changes after the journal replay, we ignore the change, and rewrite the current journal_inum to the superblock. The Linux kernel CVE team has assigned CVE-2023-53091 to this issue. Affected and fixed versions =========================== Fixed in 5.15.104 with commit 499fef2030fb754c68b1c7cb3a799a3bc1d0d925 Fixed in 6.1.21 with commit 70e66bdeae4d0f7c8e87762f425b68aedd5e8955 Fixed in 6.2.8 with commit ee0c5277d4fab920bd31345c49e193ecede9ecef Fixed in 6.3 with commit 3039d8b8692408438a618fac2776b629852663c3 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-2023-53091 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/499fef2030fb754c68b1c7cb3a799a3bc1d0d925 https://git.kernel.org/stable/c/70e66bdeae4d0f7c8e87762f425b68aedd5e8955 https://git.kernel.org/stable/c/ee0c5277d4fab920bd31345c49e193ecede9ecef https://git.kernel.org/stable/c/3039d8b8692408438a618fac2776b629852663c3
Powered by blists - more mailing lists