All reports
Low

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

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2025-68794

Probability of exploitation in the next 30 days: 0.69%

FIRST EPSS · 2026-11-18

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.

An integer underflow flaw was found in the Linux kernel's iomap layer. The iomap_adjust_read_range() function assumes block-aligned positions but can receive non-aligned inputs from certain filesystems like EROFS. This causes incorrect calculations that can underflow the length and return positions beyond the folio, leading to potential out-of-bounds access.