CVE-2026-31463
Last modified
CVE-2026-31463 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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.. EPSS estimates a 0.38% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.19, < 6.19.11 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-31463?
How severe is CVE-2026-31463?
How do I fix CVE-2026-31463?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-31458In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31459In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-3146A vulnerability has been found in libvips up to 8.18.0. The …5.5
- CVE-2026-31460In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31461In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31462In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31464In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-31465In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31466In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-31467In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-31468In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31469In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-31463?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
