Kernel crash via read-only JFS truncation
Published Apr 16, 2025 · Updated Sep 2, 2026
A JFS truncation flaw in Linux 2.6.12 through 6.14.1 allows local users to crash the kernel through writes to a read-only filesystem. jfs_truncate_nolock continues into txEnd after the JFS log has been torn down, causing a null log dereference instead of stopping modification. Triggering the path requires a writable file descriptor retained across a forced read-only remount and subsequent write or truncate activity.
Summary
What happened
A JFS truncation flaw in Linux 2.6.12 through 6.14.1 allows local users to crash the kernel through writes to a read-only filesystem. jfs_truncate_nolock continues into txEnd after the JFS log has been torn down, causing a null log dereference instead of stopping modification. Triggering the path requires a writable file descriptor retained across a forced read-only remount and subsequent write or truncate activity.
The record
- CVE
- CVE-2024-58094
- Published
- Apr 16, 2025
- Updated
- Sep 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1fee021d6cf1d41b3f6e3fd028939be8f5d5c5db
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <41da1715cd24e177678f93ee27f737b095fc838b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <77038187890ea82d237b05c8a9c4e08a38b1efcb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b5799dd77054c1ec49b0088b006c9908e256843b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b57a8983916fc2cf54fd8de3afc733c6b3d1c0e5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b98506e61e1bb6764c6711198cfab826df8ca952
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f605bc3e162f5c6faa9bd3602ce496053d06a4bb
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo