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 mis‑managing 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 that contain the faulty code path, 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 CVSS score of 9.8 indicates high severity, but the EPSS score of less than 1% suggests exploitation is unlikely at present. The vulnerability is not listed in CISA KEV. Although known exploits are not publicly documented, the potential for kernel memory corruption makes this a high‑consequence issue. Based on the description, it is inferred that the likely attack vector involves the attacker triggering a read of a file with block size configuration that mismatches the system's I/O granularity, requiring local or privileged access. Therefore, the vulnerability should be regarded as high‑risk until the fix is applied.