ext4: fix potential out of bound read in ext4_fc_replay_scan()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
5.15.876.0.66.1In the Linux kernel, the following vulnerability has been resolved:
ext4: fix potential out of bound read in ext4_fc_replay_scan()
For scan loop must ensure that at least EXT4_FC_TAG_BASE_LEN space. If remain space less than EXT4_FC_TAG_BASE_LEN which will lead to out of bound read when mounting corrupt file system image. ADD_RANGE/HEAD/TAIL is needed to add extra check when do journal scan, as this three tags will read data during scan, tag length couldn't less than data length which will read.
From the CVE record · Linux
The ext4 fast-commit replay scan can read out of bounds when mounting a corrupt filesystem image. The issue occurs if a scan tag has too little space remaining or is shorter than the data read during the scan; mounting the image is required to trigger it.
Engineers running Linux kernels with ext4 should check whether their kernel is affected; affected versions were not provided.