{"id":"CVE-2024-58085","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ntomoyo: don't emit warning in tomoyo_write_control()\n\nsyzbot is reporting too large allocation warning at tomoyo_write_control(),\nfor one can write a very very long lin…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\ntomoyo: don't emit warning in tomoyo_write_control()\n\nsyzbot is reporting too large allocation warning at tomoyo_write_control(),\nfor one can write a very very long lin…","severity":"medium","cvss":5.5,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","vendor":"linux","product":"linux_kernel","affected":["linux_kernel < 5.4.291","linux_kernel >= 5.5, < 5.10.235","linux_kernel >= 5.11, < 5.15.179","linux_kernel >= 5.16, < 6.1.129","linux_kernel >= 6.2, < 6.6.78","linux_kernel >= 6.7, < 6.12.14","linux_kernel >= 6.13, < 6.13.3"],"patched":["linux_kernel 6.13.3"],"published":"2025-03-06","updated":"2026-10-15","sourceUpdated":"2026-10-15T02:17:21.320","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2024-58085","references":[{"url":"https://git.kernel.org/stable/c/3df7546fc03b8f004eee0b9e3256369f7d096685","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/414705c0303350d139b1dc18f329fe47dfb642dd","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/b2bd5857a0d6973ebbcb4d9831ddcaebbd257be1","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/c67efabddc73171c7771d3ffe4ffa1e503ee533e","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/c9382f380e8d09209b8e5c0def0545852168be25","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/f6b37b3e12de638753bce79a2858070b9c4a4ad3","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/fe1c021eb03dae0dc9dce55e81f77a60e419a27a","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html","label":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html","label":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-265688.html","label":"0b142b55-0307-4c5a-b3c9-f314f3fb7c5e"}],"tags":["nvd","cve.org"],"epss":0.00213,"epssPercentile":0.1083,"ingestedAt":"2026-10-15T03:30:12.804Z","slug":"CVE-2024-58085","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntomoyo: don't emit warning in tomoyo_write_control()\n\nsyzbot is reporting too large allocation warning at tomoyo_write_control(),\nfor one can write a very very long line without new line character. To fix\nthis warning, I use __GFP_NOWARN rather than checking for KMALLOC_MAX_SIZE,\nfor practically a valid line should be always shorter than 32KB where the\n\"too small to fail\" memory-allocation rule applies.\n\nOne might try to write a valid line that is longer than 32KB, but such\nrequest will likely fail with -ENOMEM. Therefore, I feel that separately\nreturning -EINVAL when a line is longer than KMALLOC_MAX_SIZE is redundant.\nThere is no need to distinguish over-32KB and over-KMALLOC_MAX_SIZE.\n\n## Affected\n\n- `linux_kernel < 5.4.291`\n- `linux_kernel >= 5.5, < 5.10.235`\n- `linux_kernel >= 5.11, < 5.15.179`\n- `linux_kernel >= 5.16, < 6.1.129`\n- `linux_kernel >= 6.2, < 6.6.78`\n- `linux_kernel >= 6.7, < 6.12.14`\n- `linux_kernel >= 6.13, < 6.13.3`\n\n## Remediation\n\nUpgrade past the affected range:\n\n- `linux_kernel 6.13.3`","depth":"sunlit","depthScore":30,"depthScoreParts":{"impact":30.3,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}