What is CVE-2026-31463?

CVE-2026-31463 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10, affecting Linux kernel versions from 6.19 onward and patched in 6.19.11 and 7.0. CVE-2026-31463 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-31463?

CVE-2026-31463 has a CVSS score of 9.8 out of 10, rated Critical severity. The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-31463?

Yes, CVE-2026-31463 has been patched. Fixed versions include 6.19.11 and 7.0. If you are running Linux kernel 6.19 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-31463 actively exploited?

CVE-2026-31463 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-31463

Critical

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.

Package Linux Kernel

Published 2026-04-22

Last modified 2026-05-07

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

9.8

out of 10

Critical

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

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

Affected versions

Linux kernel versions 6.19 and later are affected. Fixed in 6.19.11, 7.0 and their respective stable series.

Affected from

≥ 6.19

Fixed in

✓ 6.19.11 6.19.x ✓ 7.0

References

The following references provide additional information about CVE-2026-31463 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Kernel patch commit
https://git.kernel.org/stable/c/4a927f670cdb0def226f9f85f42a9f19d9e09c88
Patch
Kernel patch commit
https://git.kernel.org/stable/c/bd71fb3fea9945987053968f028a948997cba8cc
Patch

Details

CVE ID CVE-2026-31463

Severity Critical

CVSS score 9.8 / 10

CVSS version 3.1

Published 2026-04-22

Modified 2026-05-07

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-31463?

CVE-2026-31463 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10 . It affects Linux kernel versions from 6.19 onward and has been patched in 6.19.11 and 7.0. CVE-2026-31463 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-31463?

CVE-2026-31463 has a CVSS score of 9.8 out of 10, rated Critical severity (CVSS 3.1). The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-31463?

Yes — CVE-2026-31463 has been patched. Fixed versions include 6.19.11 and 7.0. If you are running Linux kernel 6.19 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-31463 actively exploited?

No — CVE-2026-31463 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.