iomap: adjust read range correctly for non-block-aligned positions

Vulnerability 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.

References

• https://git.kernel.org/stable/c/82b60ffbb532d919959702768dca04c3c0500ae5
• https://git.kernel.org/stable/c/12053695c8ef5410e8cc6c9ed4c0db9cd9c82b3e
• https://git.kernel.org/stable/c/142194fb21afe964d2d194cab1fc357cbf87e899
• https://git.kernel.org/stable/c/7aa6bc3e8766990824f66ca76c19596ce10daf3e