jfs: add check read-only before truncation in jfs_truncate_nolock()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < f605bc3e162f5c6faa9bd3602ce496053d06a4bb| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s JFS truncation path can attempt a write on a read-only filesystem, causing errors. This can occur when truncation reaches jfs_truncate_nolock() on a read-only JFS filesystem; the input does not specify an attacker action, access requirement, or user interaction.
Engineers running Linux kernels with JFS should check their deployments; affected versions are not specified.