CVE-2024-58094jfs: add check read-only before truncation in jfs_truncate_nolock()
- 7.8HighCVSS base score
- 0.23%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 41 days later
· 41 days later
Published
- 17 months later
· 17 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.23% · top 87% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b98506e61e1bb6764c6711198cfab826df8ca952
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1fee021d6cf1d41b3f6e3fd028939be8f5d5c5db
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b57a8983916fc2cf54fd8de3afc733c6b3d1c0e5
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 41da1715cd24e177678f93ee27f737b095fc838b
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 77038187890ea82d237b05c8a9c4e08a38b1efcb
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f605bc3e162f5c6faa9bd3602ce496053d06a4bb
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b5799dd77054c1ec49b0088b006c9908e256843b
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.269 – ≤ 5.10.*
- unaffected 5.15.220 – ≤ 5.15.*
- unaffected 6.1.187 – ≤ 6.1.*
- unaffected 6.6.156 – ≤ 6.6.*
- unaffected 6.12.108 – ≤ 6.12.*
- unaffected 6.14.2 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References7
- https://git.kernel.org/stable/c/b98506e61e1bb6764c6711198cfab826df8ca952 (opens in a new tab)
- https://git.kernel.org/stable/c/1fee021d6cf1d41b3f6e3fd028939be8f5d5c5db (opens in a new tab)
- https://git.kernel.org/stable/c/b57a8983916fc2cf54fd8de3afc733c6b3d1c0e5 (opens in a new tab)
- https://git.kernel.org/stable/c/41da1715cd24e177678f93ee27f737b095fc838b (opens in a new tab)
- https://git.kernel.org/stable/c/77038187890ea82d237b05c8a9c4e08a38b1efcb (opens in a new tab)
- https://git.kernel.org/stable/c/f605bc3e162f5c6faa9bd3602ce496053d06a4bb (opens in a new tab)
- https://git.kernel.org/stable/c/b5799dd77054c1ec49b0088b006c9908e256843b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-11281 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-58094)Record last updated .