CVE-2025-68794
CriticalCVSS 9.8Exploitation Probability (EPSS)
Low risk37th percentile - higher than 37% of all known CVEs
Summary
In the Linux kernel iomap, iomap_adjust_read_range() assumes block-aligned positions and lengths, which is not always true (e.g., in erofs). This causes skipping too many bytes for uptodate blocks, leading to incorrect read position and length.
Risk Assessment
This could lead to reading incorrect data or exceeding the folio range, potentially causing crashes or data corruption.
Recommendation
Apply the patch that accounts for block offset when calculating how many bytes can be skipped for uptodate blocks.
Original NVD description (English source)
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.