Description
In the Linux kernel, the following vulnerability has been resolved: iomap: adjust read range correctly for non-block-aligned positions iomap_adjust_read_range() assumes that the position and length passed in are block-aligned. This is not always the case however, as shown in the syzbot generated case for erofs. This causes too many bytes to be skipped for uptodate blocks, which results in returning the incorrect position and length to read in. If all the blocks are uptodate, this underflows length and returns a position beyond the folio. Fix the calculation to also take into account the block offset when calculating how many bytes can be skipped for uptodate blocks.
Product status
9dc55f1389f9569acf9659e58dd836a9c70df217 (git) before 82b60ffbb532d919959702768dca04c3c0500ae5
9dc55f1389f9569acf9659e58dd836a9c70df217 (git) before 12053695c8ef5410e8cc6c9ed4c0db9cd9c82b3e
9dc55f1389f9569acf9659e58dd836a9c70df217 (git) before 142194fb21afe964d2d194cab1fc357cbf87e899
9dc55f1389f9569acf9659e58dd836a9c70df217 (git) before 7aa6bc3e8766990824f66ca76c19596ce10daf3e
4.19
Any version before 4.19
6.6.120 (semver)
6.12.64 (semver)
6.18.3 (semver)
6.19 (original_commit_for_fix)
References
git.kernel.org/...c/82b60ffbb532d919959702768dca04c3c0500ae5
git.kernel.org/...c/12053695c8ef5410e8cc6c9ed4c0db9cd9c82b3e
git.kernel.org/...c/142194fb21afe964d2d194cab1fc357cbf87e899
git.kernel.org/...c/7aa6bc3e8766990824f66ca76c19596ce10daf3e