| 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: <2024051752-CVE-2023-52685-64c5@gregkh> Date: Fri, 17 May 2024 16:26:58 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2023-52685: pstore: ram_core: fix possible overflow in persistent_ram_init_ecc() Description =========== In the Linux kernel, the following vulnerability has been resolved: pstore: ram_core: fix possible overflow in persistent_ram_init_ecc() In persistent_ram_init_ecc(), on 64-bit arches DIV_ROUND_UP() will return 64-bit value since persistent_ram_zone::buffer_size has type size_t which is derived from the 64-bit *unsigned long*, while the ecc_blocks variable this value gets assigned to has (always 32-bit) *int* type. Even if that value fits into *int* type, an overflow is still possible when calculating the size_t typed ecc_total variable further below since there's no cast to any 64-bit type before multiplication. Declaring the ecc_blocks variable as *size_t* should fix this mess... Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool. The Linux kernel CVE team has assigned CVE-2023-52685 to this issue. Affected and fixed versions =========================== Issue introduced in 3.4 with commit 9cc05ad97c57 and fixed in 4.19.306 with commit 3b333cded94f Issue introduced in 3.4 with commit 9cc05ad97c57 and fixed in 5.4.268 with commit d1fe1aede684 Issue introduced in 3.4 with commit 9cc05ad97c57 and fixed in 5.10.209 with commit acd413da3e1f Issue introduced in 3.4 with commit 9cc05ad97c57 and fixed in 5.15.148 with commit 8fb12524c86b Issue introduced in 3.4 with commit 9cc05ad97c57 and fixed in 6.1.75 with commit 48dcfc42ce70 Issue introduced in 3.4 with commit 9cc05ad97c57 and fixed in 6.6.14 with commit a34946ec3de8 Issue introduced in 3.4 with commit 9cc05ad97c57 and fixed in 6.7.2 with commit f9b891a7e8fc Issue introduced in 3.4 with commit 9cc05ad97c57 and fixed in 6.8 with commit 86222a8fc16e 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-52685 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/pstore/ram_core.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/3b333cded94fbe5ce30d699b316c4715151268ae https://git.kernel.org/stable/c/d1fe1aede684bd014714dacfdc75586a9ad38657 https://git.kernel.org/stable/c/acd413da3e1f37582207cd6078a41d57c9011918 https://git.kernel.org/stable/c/8fb12524c86bdd542a54857d5d076b1b6778c78c https://git.kernel.org/stable/c/48dcfc42ce705b652c0619cb99846afc43029de9 https://git.kernel.org/stable/c/a34946ec3de88a16cc3a87fdab50aad06255a22b https://git.kernel.org/stable/c/f9b891a7e8fcf83901f8507241e23e7420103b61 https://git.kernel.org/stable/c/86222a8fc16ec517de8da2604d904c9df3a08e5d
Powered by blists - more mailing lists