jfs: truncate good inode pages when hard link is 0
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 32983696a48a6c41d99f3eca82ba7510a552d843 · < df3fd8daf278eca365f221749ae5b728e8382a04| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
jfs: truncate good inode pages when hard link is 0
The fileset value of the inode copy from the disk by the reproducer is AGGR_RESERVED_I. When executing evict, its hard link number is 0, so its inode pages are not truncated. This causes the bugon to be triggered when executing clear_inode() because nrpages is greater than 0.
From the CVE record · Linux
The Linux kernel's JFS code can leave inode pages untruncated when evicting an inode whose hard-link count is zero and whose on-disk fileset value is AGGR_RESERVED_I. This can trigger a BUG_ON in clear_inode() because pages remain. The input does not specify how an attacker could reach this condition or any authentication or user-interaction requirements.
Engineers running Linux kernels with JFS should check their versions against the vendor advisory; affected versions are not specified in the input.