| 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: <2025082210-CVE-2024-58239-dd4f@gregkh> Date: Fri, 22 Aug 2025 15:01:11 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2024-58239: tls: stop recv() if initial process_rx_list gave us non-DATA From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: tls: stop recv() if initial process_rx_list gave us non-DATA If we have a non-DATA record on the rx_list and another record of the same type still on the queue, we will end up merging them: - process_rx_list copies the non-DATA record - we start the loop and process the first available record since it's of the same type - we break out of the loop since the record was not DATA Just check the record type and jump to the end in case process_rx_list did some work. The Linux kernel CVE team has assigned CVE-2024-58239 to this issue. Affected and fixed versions =========================== Issue introduced in 5.1 with commit 692d7b5d1f9125a1cf0595e979e3b5fb7210547e and fixed in 5.4.270 with commit f310143961e2d9a0479fca117ce869f8aaecc140 Issue introduced in 5.1 with commit 692d7b5d1f9125a1cf0595e979e3b5fb7210547e and fixed in 5.10.211 with commit 31e10d6cb0c9532ff070cf50da1657c3acee9276 Issue introduced in 5.1 with commit 692d7b5d1f9125a1cf0595e979e3b5fb7210547e and fixed in 5.15.150 with commit 4338032aa90bd1d5b33a4274e8fa8347cda5ee09 Issue introduced in 5.1 with commit 692d7b5d1f9125a1cf0595e979e3b5fb7210547e and fixed in 6.1.80 with commit 6756168add1c6c3ef1c32c335bb843a5d1f99a75 Issue introduced in 5.1 with commit 692d7b5d1f9125a1cf0595e979e3b5fb7210547e and fixed in 6.6.19 with commit 3b952d8fdfcf6fd8ea0b8954bc9277642cf0977f Issue introduced in 5.1 with commit 692d7b5d1f9125a1cf0595e979e3b5fb7210547e and fixed in 6.7.7 with commit a4ed943882a8fc057ea5a67643314245e048bbdd Issue introduced in 5.1 with commit 692d7b5d1f9125a1cf0595e979e3b5fb7210547e and fixed in 6.8 with commit fdfbaec5923d9359698cbb286bc0deadbb717504 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-2024-58239 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: net/tls/tls_sw.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/f310143961e2d9a0479fca117ce869f8aaecc140 https://git.kernel.org/stable/c/31e10d6cb0c9532ff070cf50da1657c3acee9276 https://git.kernel.org/stable/c/4338032aa90bd1d5b33a4274e8fa8347cda5ee09 https://git.kernel.org/stable/c/6756168add1c6c3ef1c32c335bb843a5d1f99a75 https://git.kernel.org/stable/c/3b952d8fdfcf6fd8ea0b8954bc9277642cf0977f https://git.kernel.org/stable/c/a4ed943882a8fc057ea5a67643314245e048bbdd https://git.kernel.org/stable/c/fdfbaec5923d9359698cbb286bc0deadbb717504
Powered by blists - more mailing lists