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.
2025-04-16T15:15:53.330
2025-10-28T18:54:50.797
Analyzed
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSSv3.1: 5.5 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | linux | linux_kernel | < 6.14.2 | Yes |
| Operating System | linux | linux_kernel | 2.6.12 | Yes |
| Operating System | linux | linux_kernel | 2.6.12 | Yes |
| Operating System | linux | linux_kernel | 2.6.12 | Yes |
| Operating System | linux | linux_kernel | 2.6.12 | Yes |
| Operating System | linux | linux_kernel | 2.6.12 | Yes |