{"uuid": "726fa625-4e87-4946-b963-930f1770ea6f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58094", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14780", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58094\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\njfs: add check read-only before truncation in jfs_truncate_nolock()\n\nAdded a check for \"read-only\" mode in the `jfs_truncate_nolock`\nfunction to avoid errors related to writing to a read-only\nfilesystem.\n\nCall stack:\n\nblock_write_begin() {\n  jfs_write_failed() {\n    jfs_truncate() {\n      jfs_truncate_nolock() {\n        txEnd() {\n          ...\n          log = JFS_SBI(tblk->sb)->log;\n          // (log == NULL)\n\nIf the `isReadOnly(ip)` condition is triggered in\n`jfs_truncate_nolock`, the function execution will stop, and no\nfurther data modification will occur. Instead, the `xtTruncate`\nfunction will be called with the \"COMMIT_WMAP\" flag, preventing\nmodifications in \"read-only\" mode.\n\ud83d\udccf Published: 2025-04-16T14:11:43.298Z\n\ud83d\udccf Modified: 2025-05-04T10:09:57.136Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/f605bc3e162f5c6faa9bd3602ce496053d06a4bb\n2. https://git.kernel.org/stable/c/b5799dd77054c1ec49b0088b006c9908e256843b", "creation_timestamp": "2025-05-04T11:18:58.000000Z"}