{"uuid": "1a9384c9-b839-4b24-b392-189adcb540b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58085", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/6706", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58085\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: 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 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\ud83d\udccf Published: 2025-03-06T16:22:32.761Z\n\ud83d\udccf Modified: 2025-03-06T16:22:32.761Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f\n2. https://git.kernel.org/stable/c/fe1c021eb03dae0dc9dce55e81f77a60e419a27a\n3. https://git.kernel.org/stable/c/c9382f380e8d09209b8e5c0def0545852168be25\n4. https://git.kernel.org/stable/c/414705c0303350d139b1dc18f329fe47dfb642dd\n5. https://git.kernel.org/stable/c/3df7546fc03b8f004eee0b9e3256369f7d096685", "creation_timestamp": "2025-03-06T16:34:06.000000Z"}