---
id: CVE-2024-58094
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  jfs: add check read-only before truncation in jfs_truncate_nolock()

  Added a check for "read-only" mode in the `jfs_truncate_nolock`
  function to avoid errors related to…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  jfs: add check read-only before truncation in jfs_truncate_nolock()

  Added a check for "read-only" mode in the `jfs_truncate_nolock`
  function to avoid errors related to…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 2.6.13, < 6.14.2'
  - linux_kernel = 2.6.12
patched:
  - linux_kernel 6.14.2
published: '2025-04-16'
updated: '2026-09-02'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-58094'
references:
  - url: 'https://git.kernel.org/stable/c/1fee021d6cf1d41b3f6e3fd028939be8f5d5c5db'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/41da1715cd24e177678f93ee27f737b095fc838b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/77038187890ea82d237b05c8a9c4e08a38b1efcb'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b5799dd77054c1ec49b0088b006c9908e256843b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b57a8983916fc2cf54fd8de3afc733c6b3d1c0e5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b98506e61e1bb6764c6711198cfab826df8ca952'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f605bc3e162f5c6faa9bd3602ce496053d06a4bb'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00225
epssPercentile: 0.11735
ingestedAt: '2026-09-02T13:44:40.796Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

jfs: add check read-only before truncation in jfs_truncate_nolock()

Added a check for "read-only" mode in the `jfs_truncate_nolock`
function to avoid errors related to writing to a read-only
filesystem.

Call stack:

block_write_begin() {
  jfs_write_failed() {
    jfs_truncate() {
      jfs_truncate_nolock() {
        txEnd() {
          ...
          log = JFS_SBI(tblk->sb)->log;
          // (log == NULL)

If the `isReadOnly(ip)` condition is triggered in
`jfs_truncate_nolock`, the function execution will stop, and no
further data modification will occur. Instead, the `xtTruncate`
function will be called with the "COMMIT_WMAP" flag, preventing
modifications in "read-only" mode.

## Affected

- `linux_kernel >= 2.6.13, < 6.14.2`
- `linux_kernel = 2.6.12`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.14.2`