CVE-2024-58094: jfs: add check read-only before truncation in jfs_truncate_nolock()
In the Linux kernel, the following vulnerability has been resolved:
jfs: add check read-only before truncation in jfstruncatenolock()
Added a check for "read-only" mode in the jfstruncatenolock function to avoid errors related to writing to a read-only filesystem.
Call stack:
blockwritebegin() { jfswritefailed() { jfstruncate() { jfstruncatenolock() { txEnd() { ... log = JFSSBI(tblk->sb)->log; // (log == NULL)
If the isReadOnly(ip) condition is triggered in jfstruncatenolock, the function execution will stop, and no further data modification will occur. Instead, the xtTruncate function will be called with the "COMMITWMAP" flag, preventing modifications in "read-only" mode.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-58094?
CVE-2024-58094 has been classified with a severity level that underscores the importance of addressing the read-only mode issue in the jfs_truncate_nolock function.
How do I fix CVE-2024-58094?
To fix CVE-2024-58094, ensure you are using an updated version of the Linux Kernel that includes the recent patch for the jfs_truncate_nolock function.
What does CVE-2024-58094 affect?
CVE-2024-58094 specifically affects the Linux Kernel, particularly the jfs file system when it is in read-only mode.
What type of vulnerability is CVE-2024-58094?
CVE-2024-58094 is a software vulnerability related to improper handling of file system operations under read-only conditions.
Who is impacted by CVE-2024-58094?
Users and administrators running vulnerable versions of the Linux Kernel that utilize the jfs file system are impacted by CVE-2024-58094.