CVE-2024-58094

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.

Red Hat has evaluated this vulnerability as Moderate severity because exploitation requires local access to trigger write failures on a JFS filesystem, and the impact is confined to a denial of service through a system crash. Confidentiality and integrity of system data are not compromised by this issue. Furthermore, JFS is a legacy filesystem that is not utilized in default enterprise configurations, and modern supported Red Hat Enterprise Linux releases do not include the vulnerable code.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.