| 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: <2025011142-CVE-2024-49571-c86d@gregkh> Date: Sat, 11 Jan 2025 13:35:46 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg Description =========== In the Linux kernel, the following vulnerability has been resolved: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg When receiving proposal msg in server, the field iparea_offset and the field ipv6_prefixes_cnt in proposal msg are from the remote client and can not be fully trusted. Especially the field iparea_offset, once exceed the max value, there has the chance to access wrong address, and crash may happen. This patch checks iparea_offset and ipv6_prefixes_cnt before using them. The Linux kernel CVE team has assigned CVE-2024-49571 to this issue. Affected and fixed versions =========================== Issue introduced in 4.16 with commit e7b7a64a8493d47433fd003efbe6543e3f676294 and fixed in 5.10.233 with commit 846bada23bfcdeb83621b045ed85dc06c7833ff0 Issue introduced in 4.16 with commit e7b7a64a8493d47433fd003efbe6543e3f676294 and fixed in 5.15.176 with commit f10635268a0a49ee902a3b63b5dbb76f4fed498e Issue introduced in 4.16 with commit e7b7a64a8493d47433fd003efbe6543e3f676294 and fixed in 6.1.122 with commit 62056d1592e63d85e82357ee2ae6a6a294f440b0 Issue introduced in 4.16 with commit e7b7a64a8493d47433fd003efbe6543e3f676294 and fixed in 6.6.68 with commit 91a7c27c1444ed4677b83fd5308d2cf03f5f0851 Issue introduced in 4.16 with commit e7b7a64a8493d47433fd003efbe6543e3f676294 and fixed in 6.12.7 with commit 47ce46349672a7e0c361bfe39ed0b22e824ef4fb Issue introduced in 4.16 with commit e7b7a64a8493d47433fd003efbe6543e3f676294 and fixed in 6.13-rc4 with commit a29e220d3c8edbf0e1beb0f028878a4a85966556 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-49571 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/smc/af_smc.c net/smc/smc_clc.c net/smc/smc_clc.h 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/846bada23bfcdeb83621b045ed85dc06c7833ff0 https://git.kernel.org/stable/c/f10635268a0a49ee902a3b63b5dbb76f4fed498e https://git.kernel.org/stable/c/62056d1592e63d85e82357ee2ae6a6a294f440b0 https://git.kernel.org/stable/c/91a7c27c1444ed4677b83fd5308d2cf03f5f0851 https://git.kernel.org/stable/c/47ce46349672a7e0c361bfe39ed0b22e824ef4fb https://git.kernel.org/stable/c/a29e220d3c8edbf0e1beb0f028878a4a85966556
Powered by blists - more mailing lists