CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions
In the Linux kernel, the following vulnerability has been resolved:
iomap: adjust read range correctly for non-block-aligned positions
iomapadjustreadrange() 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68794?
The severity of CVE-2025-68794 is considered moderate due to its potential impact on system performance.
How do I fix CVE-2025-68794?
To fix CVE-2025-68794, update to the latest version of the Linux kernel that addresses this vulnerability.
What systems are affected by CVE-2025-68794?
CVE-2025-68794 affects Linux kernel versions that utilize the iomap framework.
What is the impact of CVE-2025-68794 on system security?
CVE-2025-68794 may lead to incorrect data read operations, potentially compromising data integrity.
What is the nature of the issue described in CVE-2025-68794?
CVE-2025-68794 involves improper handling of read range adjustments for non-block-aligned positions in the iomap.