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: <2025030634-CVE-2024-58085-1af4@gregkh> Date: Thu, 6 Mar 2025 17:22:36 +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-58085: tomoyo: don't emit warning in tomoyo_write_control() Description =========== In the Linux kernel, the following vulnerability has been resolved: tomoyo: don't emit warning in tomoyo_write_control() syzbot is reporting too large allocation warning at tomoyo_write_control(), for one can write a very very long line without new line character. To fix this warning, I use __GFP_NOWARN rather than checking for KMALLOC_MAX_SIZE, for practically a valid line should be always shorter than 32KB where the "too small to fail" memory-allocation rule applies. One might try to write a valid line that is longer than 32KB, but such request will likely fail with -ENOMEM. Therefore, I feel that separately returning -EINVAL when a line is longer than KMALLOC_MAX_SIZE is redundant. There is no need to distinguish over-32KB and over-KMALLOC_MAX_SIZE. The Linux kernel CVE team has assigned CVE-2024-58085 to this issue. Affected and fixed versions =========================== Fixed in 6.1.129 with commit a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f Fixed in 6.6.78 with commit fe1c021eb03dae0dc9dce55e81f77a60e419a27a Fixed in 6.12.14 with commit c9382f380e8d09209b8e5c0def0545852168be25 Fixed in 6.13.3 with commit 414705c0303350d139b1dc18f329fe47dfb642dd Fixed in 6.14-rc1 with commit 3df7546fc03b8f004eee0b9e3256369f7d096685 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-58085 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: security/tomoyo/common.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/a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f https://git.kernel.org/stable/c/fe1c021eb03dae0dc9dce55e81f77a60e419a27a https://git.kernel.org/stable/c/c9382f380e8d09209b8e5c0def0545852168be25 https://git.kernel.org/stable/c/414705c0303350d139b1dc18f329fe47dfb642dd https://git.kernel.org/stable/c/3df7546fc03b8f004eee0b9e3256369f7d096685
Powered by blists - more mailing lists