CVE-2026-31463

published 22 Apr 2026 · updated 13 Nov 2026

iomap: fix invalid folio access when i_blkbits differs from I/O granularity

9.8CriticalCVSS 9.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel bd71fb3fea9945987053968f028a948997cba8cc, Kernel 6.19.11 and Kernel 4a927f670cdb0def226f9f85f42a9f19d9e09c88.

In the Linux kernel, the following vulnerability has been resolved: iomap: fix invalid folio access when i_blkbits differs from I/O granularity Commit aa35dd5cbc06 ("iomap: fix invalid folio access after folio_end_read()") partially addressed invalid folio access for folios without an ifs attached, but it did not handle the case where 1 << inode->i_blkbits matches the folio size but is different from the granularity used for the IO, which means IO can be submitted for less than the full folio for the !ifs case. In this case, the condition: if (*bytes_submitted == folio_len) ctx->cur_folio = NULL; in iomap_read_folio_iter() will not invalidate ctx->cur_folio, and iomap_read_end() will still be called on the folio even though the IO helper owns it and will finish the read on it. Fix this by unconditionally invalidating ctx->cur_folio for the !ifs case.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=b2f35ac4146d32d4424aaa941bbc681f12c1b9e6 <bd71fb3fea9945987053968f028a948997cba8cc, =7.0, >=6.19 <6.19.11, =6.19, >=b2f35ac4146d32d4424aaa941bbc681f12c1b9e6 <4a927f670cdb0def226f9f85f42a9f19d9e09c88bd71fb3fea9945987053968f028a948997cba8cc, 6.19.11, 4a927f670cdb0def226f9f85f42a9f19d9e09c88
linux-kernel: Kernel>=6.19.0 <6.19.116.19.11

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-31463 severity on Zeptric[![CVE-2026-31463](https://zeptric.io/badge/cve/CVE-2026-31463.svg)](https://zeptric.io/cve/CVE-2026-31463)