{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2024-58094","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-03-06T15:52:09.188Z","datePublished":"2025-04-16T14:11:43.298Z","dateUpdated":"2026-08-05T11:47:41.635Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T11:47:41.635Z"},"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The vulnerability is triggered by a local write(2)/truncate on a file residing on a mounted JFS filesystem, reaching jfs_write_begin → jfs_write_failed → jfs_truncate_nolock. There is no network-facing consumer of this path.\nAC:L - With an fd held open across a forced remount-ro (mount -o remount,ro,force or SysRq emergency remount) the trigger is deterministic, and the remount,nointegrity path in jfs_reconfigure() tears down the log with no SB_RDONLY set and no writer hold-off, leaving a multi-second window an attacker can hammer with a write loop. No memory-layout or victim-state condition outside the attacker's influence is needed.\nPR:L - The memory-unsafe operation executes in the context of an ordinary unprivileged process's buffered write on a JFS file; the read-only/log-teardown transition is a routine system event (shutdown remount, emergency remount, integrity-flag remount, removable-media handling) rather than something the attacker must supply. Basic local user access with a writable fd on a JFS volume suffices.\nUI:N - No victim action is required — the attacker's own write(2) call drives the entire path through xtTruncate() and txEnd(0). The filesystem is already mounted in the targeted deployment scenario.\nS:U - The wild-pointer read/write, lock corruption and filesystem metadata damage all occur within the kernel's own security authority. No VM, IOMMU, or sandbox boundary is crossed.\nC:H - txEnd(0) dereferences TxBlock[0].sb, which is uninitialized vmalloc memory holding stale kernel data, and then chases it a second time (JFS_SBI(tblk->sb)->log), while TXN_WAKEUP walks an uninitialized wait_queue_head's garbage list pointers. This uninitialized-memory-driven corruption is groomable and leverageable for kernel memory disclosure.\nI:H - Without the fix, xtTruncate() runs with COMMIT_PWMAP and mutates xtree metadata and the persistent block map of a filesystem that must not be modified — the fix exists precisely so that \"no further data modification will occur\". Additionally, `--log->active` performs a decrement write through a pointer derived from uninitialized memory, and TxAnchor.freetid is corrupted to 0 so later transactions reuse the uninitialized TxBlock[0].\nA:H - The immediate observed result is a kernel oops (\"BUG: unable to handle kernel paging request\"/null-ptr-deref) in txEnd(). It occurs while the global TXN_LOCK spinlock, the inode commit_mutex and IWRITE_LOCK are held, so the locks are never released and every subsequent JFS operation on the system deadlocks."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/jfs/inode.c"],"versions":[{"version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","lessThan":"f605bc3e162f5c6faa9bd3602ce496053d06a4bb","status":"affected","versionType":"git"},{"version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","lessThan":"b5799dd77054c1ec49b0088b006c9908e256843b","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/jfs/inode.c"],"versions":[{"version":"2.6.12","status":"affected"},{"version":"0","lessThan":"2.6.12","status":"unaffected","versionType":"semver"},{"version":"6.14.2","lessThanOrEqual":"6.14.*","status":"unaffected","versionType":"semver"},{"version":"6.15","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.12","versionEndExcluding":"6.14.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.12","versionEndExcluding":"6.15"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/f605bc3e162f5c6faa9bd3602ce496053d06a4bb"},{"url":"https://git.kernel.org/stable/c/b5799dd77054c1ec49b0088b006c9908e256843b"}],"title":"jfs: add check read-only before truncation in jfs_truncate_nolock()","x_generator":{"engine":"bippy-1.2.0"}}}}