CVE-2026-31463

9.8 CRITICAL 0.4% exploit odds Fix listed Other OS & kernel

What it is

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.

At a glance

Exploitability: Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
Exploit odds: 0.4% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2026-04-22 14:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-17 10:33 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.4% in the next 30 days (EPSS).
Severity: 9.8 CRITICAL (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2026-04-22 14:16 UTC
Last modified: 2026-06-17 10:33 UTC
Exploit probability: 0.4% · EPSS, next 30 days
Record status: Analyzed

Affected

Linux Kernel < 6.19.11
Linux Kernel 7.0

Attack profile CVSS 3.1 · 9.8

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-31463.md and follow it. Check whether this project is affected by CVE-2026-31463. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record