The Linux kernel contains an issue in the iomap subsystem that allows an invalid folio to be accessed when the inode block size differs from the I/O granularity. In this scenario the read iterator fails to clear the current folio, causing the end helper to operate on a folio that is still owned by the I/O helper. This mismanaging of kernel memory can result in corruption of kernel data structures, potentially giving an attacker the ability to execute arbitrary code or crash the system. The weakness stems from improper resource handling and read iterator logic.

This vulnerability affects all releases of the Linux kernel in which the faulty code path exists, until the patch identified by commit aa35dd5cbc06 is applied. The affected systems are any Linux installations running a kernel prior to this commit, regardless of distribution or architecture, because the flaw resides in core kernel files. The exact version range cannot be listed because the data does not provide a version list.

No CVSS or EPSS scores are available, and the issue is not listed in CISA KEV. The lack of publicly documented exploitation reduces immediate risk, but kernel memory corruption remains a high‑consequence issue. The likely attack vector requires the attacker to cause the kernel to read from a file whose block size configuration triggers the mis‑aligned i_blkbits pattern, which implies local or privileged access. Consequently, the vulnerability should be treated as a high‑risk kernel issue until the relevant patch is deployed.