CVE-2025-68794
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2026-01-13

Last updated on: 2026-01-14

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-13
Last Modified
2026-01-14
Generated
2026-05-07
AI Q&A
2026-01-14
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is in the Linux kernel's iomap subsystem, specifically in the function iomap_adjust_read_range(). The function incorrectly assumes that the position and length parameters are block-aligned, which is not always true. This causes the function to skip too many bytes for uptodate blocks, resulting in incorrect position and length values being returned for reading. In cases where all blocks are uptodate, the length underflows and the position returned goes beyond the folio. The fix involves adjusting the calculation to consider the block offset properly when determining how many bytes to skip.


How can this vulnerability impact me? :

The vulnerability can cause incorrect read operations in the Linux kernel's iomap subsystem, potentially leading to reading incorrect data or data corruption due to wrong position and length calculations. This may affect system stability or data integrity when accessing filesystems that trigger this condition.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart