Skip to content
Fencer Vulns
high 7.8

CVE-2024-58094 json

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

published 2025-04-16 18 mo ago modified 2026-09-02 2 mo ago also EUVD-2025-11281

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

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 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.

Patch / fix

  • Linux Linux 5.10.269, 5.15.220, 6.1.187, 6.6.156, 6.12.108, 6.14.2, 6.15
  • linux Debian 12 6.1.187-1
  • linux Debian 13 6.12.111-1
  • linux Debian 14 6.16.3-1
  • linux-6.12 Debian 12 6.12.111-1~deb12u1

debian advisories DEBIAN-CVE-2024-58094

  • linux Ubuntu 22.04 LTS 5.15.0-202.212
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
  • linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
  • linux-kvm Ubuntu 22.04 LTS 5.15.0-1111.116
  • linux-azure Ubuntu 22.04 LTS 5.15.0-1125.134
  • linux-gkeop Ubuntu 22.04 LTS 5.15.0-1102.110

ubuntu advisories UBUNTU-CVE-2024-58094

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.3.1
  • kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.3.1
  • kernel-rt_debug Real Time Module 15 SP7 6.4.0-150700.7.3.1
  • kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.3.1
  • kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.3.1
  • kernel-syms-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.3.1
  • kernel-source-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.3.1
  • kernel-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.39.1

suse advisories SUSE-SU-2025:01972-1SUSE-SU-2025:01967-1SUSE-SU-2025:01964-1SUSE-SU-2025:01951-1SUSE-SU-2025:01919-1SUSE-SU-2025:01707-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-58094 updated cvss 5.5

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

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.